Create library and pipeline for gateway verification

[aakano684]

Purpose

• Create Library and pipeline for gateway verification

Does this introduce a breaking change?

[ ] Yes
[x] No

Pull Request Type

What kind of change does this Pull Request introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation content changes
[ ] Other... Please describe:

How to Test

• Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

• Test the code

What to Check

Verify that the following are valid

• ...

Other Information

[noce2]

Please could we change the name of the repository? The current name it has doesn't match the library's intent (it's for http request signature verification in general and so could be reused by our components if the need arose) as well as by someone else who might want to use the same technique.

[noce2]

2 questions, nothing particularly major.

[noce2]

Please could we add some notes on how the library should be used? First from how does this dependency get added into your pom.xml and second from where does it get included in my code.

[noce2]

What did we have to change to the implementation class in bringing it here? As the handler isn't here I can't easily tell.

[noce2]

On reflection I think we probably want to save minutes and not build feature branches by default? I assume GitHub workflows have similar restrictions to Azure DevOps?