Alter email to base64, because the regex enconding

[deividMatos]

Proposed changes

Changed the user email to base64 for the k8s labels objects, regarding to this issue. #3634
This was implemented based on this comment for PR #3648.

Types of changes

What types of changes does your code introduce to Litmus? Put an x in the boxes that apply

• New feature (non-breaking change which adds functionality)
• Bugfix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation Update (if none of the other choices applies)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

• I have read the CONTRIBUTING doc
• I have signed the commit for DCO to be passed.
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works (if appropriate)
• I have added necessary documentation (if appropriate)

Dependency

• Please add the links to the dependent PR need to be merged before this (if any).

Special notes for your reviewer:

[imrajdas]

Thanks, @deividMatos for this PR.

One quest- Have you tested it in your local dev?

[deividMatos]

Thanks, @deividMatos for this PR.

One quest- Have you tested it in your local dev?

Yes, I tested it with a member of my squad and we created several flows to test in different scenarios, all in local dev

[amityt]

Thanks @deividMatos for this PR! This will unblock a lot of users! Have test the changes and will take it as part of our next release! 🚀

[ludovic-pourrat]

Thanks @deividMatos works for us too !

[ludovic-pourrat]

Hi,

Could we decode this in the UI to display the originating user email ?

[amityt]

Hi @ludovic-pourrat , this is already handled in the UI. Attaching a screenshot for reference!

[ludovic-pourrat]

@amityt my bad my graphql-server was not updated, after applying the patch on my deployment, many thanks for your answer !