Change jwt parsing to use URL_SAFE_NO_PAD

[Hinton]

Type of change

- [x] Bug fix
- [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
- [ ] Build/deploy pipeline (DevOps)
- [ ] Other

Objective

JWT should be url encoded and never use padding.

Before you submit

• Please add unit tests where it makes sense to do so (encouraged but not required)

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (1067d35) 45.21% compared to head (3b69483) 45.21%.

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #450   +/-   ##
=======================================
  Coverage   45.21%   45.21%           
=======================================
  Files         153      153           
  Lines        6918     6918           
=======================================
  Hits         3128     3128           
  Misses       3790     3790           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[MGibson1]

This is the default, right?

[Hinton]

This follows the JWT spec, and how we encode our tokens.