fix(ocpi-2.2.1): Fixed usage of tokens & review PlatformRepository

[lilgallon]

Change notes

only for 2.2.1

Credentials logic

The credentials logic completely changed. Token B and Token C were replaced by Client Token and Server Token. The Token A usage stays the same.

The Credentials Token A is used by the sender to communicate with the receiver (only when initiating registration). After registration, it is invalidated.

Then, there are two tokens, and the token to use is specified by the registration process.

• When you are the receiver during registration:
  • OCPI Token B is the client token, the one you have to use to send requests
  • OCPI Token C is the server token, the one you have to use to check if requests are properly authenticated
• When you are the sender during registration:
  • OCPI Token B is the server token, the one you have to use to check if requests are properly authenticated
  • OCPI Token C is the client token, the one you have to use to send requests

This is why we do not use OCPI's token B and token C naming. According to who you are in the registration process, you have to use a different token. Using "Client Token" and "Server Token" simplifies that process of picking the right token for the right operation.

Before these changes, the library would not work when used while being the receiver of the registration process.

PlatformRepository modifications

Unused methods are removed. Some were renamed and their signature updated to match the new credentials logic. The unregistration is now in one unique method, rather than 5 different methods.

Migration guide

It's a breaking change, it also breaks your Platform objects.

You will have to update your PlatformRepository implementation to match the new interface. Everything is documented in the file. You have to re-register with your partners. Or you can mnually update your Platform object to reflect the changes (clientToken / serverToken instead of tokenB / tokenC).

Notes

This will allow us to bump the lib to 0.1.0 as it should now work properly, and it's now usable (not production ready yet obvisouly).

[xhanin]

I have a few comments, but they are beyond the scope of this PR, and could be discussed / handled in another PR.
Therefore this PR is good for me as is, and the updates for the other versions can be handled separately in other PR / issues.

[sonarqubecloud]

Please retry analysis of this Pull-Request directly on SonarCloud.