[chore] Fix request headers

[theBeginner86]

Notes for Reviewers

This PR fixes the request headers for requesting MesheryAPI and MesheryCloudAPI by setting the missing provider-token and provider key in cookies

This PR fixes #

Signed commits

• Yes, I signed my commits.

[theBeginner86]

After merging this PR we still need to fix the endpoint for triggering the workflow. Currently its seems bogus as its returning 404.
I don't remember the endpoint so if any of maintainer can please update the endpoint then we should be good 👍

[theBeginner86]

Updates:

1. Added support to trigger snapshot workflow in meshery/helm-kanvas-snapshot
2. Added missing kanvas snapshot workflow
3. Removed required email field

This is how it would work:

[theBeginner86]

@leecalcote @jerensl

Though the snapshot service itself is failing for past 2 days, once its fixed then we should be good.
https://github.com/meshery/meshery/actions/workflows/kanvas.yml
https://github.com/meshery/meshery.io/actions/workflows/kanvas.yml

[theBeginner86]

Can someone with privileges add the missing GitHub access token that can trigger workflow? It would fix the failing check. Then we can merge and release. https://github.com/meshery/helm-kanvas-snapshot/actions/runs/12338342779/job/34433184955?pr=71

Fixed ✅

[jerensl]

Can someone with privileges add the missing GitHub access token that can trigger workflow? It would fix the failing check. Then we can merge and release

https://github.com/meshery/helm-kanvas-snapshot/actions/runs/12338342779/job/34433184955?pr=71

GH_ACCESS_TOKEN is already being set as repository secret

[Aijeyomah]

@theBeginner86 Is this a temporary fix for the unmerged PR in the meshery cloud that already handles triggering of the workflow?