Add support for public and private header parameters

[daniel-moh]

Adds support for working with arbitrary header parameters as per RFC-7515, 4.2/3 (JWS) and RFC-1716-4.2/3 (JWE).

Special Considerations

• This API ensures that the dictionary used to access parameters and the underlying JSON data representation stay in sync. This avoids any situations where the parameters dictionary contains a value that cannot be represented in JSON and therefore the resulting JWS/E header does not.
• It is also guaranteed that required header parameters are not removed or altered via the new API. Required header parameters must be set when initializing the JWS/E header.

Misc

Continuing what we started in #310, this adds deterministic JSON encoding (.sortedKeys) to the header JSON representation.

This outdates and closes #282.

[haeser]

👏🏼 very nice and clean approach that fits neatly.

[sonarcloud]

Quality Gate passed

Issues
0 New issues
2 Accepted issues

Measures
0 Security Hotspots
97.3% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud