Feat/jwt-auth

[wshino]

Description

This is the draft PR, it doesn't include any test cases for JwtAuth. We'll discuss the specs in this PR and I'll brush up on implementation and testing.

Type of Change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have discussed with the team prior to submitting this PR
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• My changes generate no new warnings
• New and existing unit tests pass locally with my changes

[wshino]

@shreyas-londhe
For jwt-tx-builder, I want to make sure that this process is not necessary because I do not think that the specification to create a JwtAuth contract for each different accountSalt. If you want to create a JwtAuth for each domainName or azp, please let me know

[Divide-By-0]

why is this being merged into chainlink-fn? those should be two seperate PRs up to main -- we want to merge this ASAP but chainlink functions is fine if it takes a few more days

[wshino]

@Divide-By-0

why is this being merged into chainlink-fn? those should be two seperate PRs up to main -- we want to merge this ASAP but chainlink functions is fine if it takes a few more days

This PR is forked from the chainlink function branch to make changes
If we want to merge to the main branch immediately, I'll create another PR from the main branch. What do you think about this proposal? The deploy script and integration test are the remaining work.

As for Chainlink Functions, it will take a little more time.