feature: OCPP 2.1 support

[xBlaz3kx]

Proposed changes

OCPP 2.1:

• Added new profiles: DER Control, Battery swapping, V2X
• Reused and updated existing OCPP 2.0.1 profiles (changed according to spec)
• Unit tests
• Handlers and feature registration

OCPPJ:

• Initial support for SEND and CALLERROR_RESULT messages
• Integration tests for newly supported SEND and CALLERROR_RESULT

Misc:

• Docs updates
• Examples

Types of changes

What types of changes does your code introduce?
Put an x in the boxes that apply

• Bugfix (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)
• Documentation Update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of
them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before
merging your code.

• I have read the CONTRIBUTING doc
• I have signed the CLA
• Lint and unit tests pass locally with my changes
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• Any dependent changes have been merged and published in downstream modules

[xBlaz3kx]

Ill need a couple of reviewers to double check my work - if all the fields are mapped, named and validated correctly.
We can add field docs after the fact.

[sderkacs]

Hi xBlaz3kx,

I noticed that the DynUpdateTime field of ocpp2.1 ChargingProfile is of type DateTime from ocpp2.0.1/types.

[xBlaz3kx]

Hi xBlaz3kx,

I noticed that the DynUpdateTime field of ocpp2.1 ChargingProfile is of type DateTime from ocpp2.0.1/types.

Hey,

thanks for pointing it out! Even though this wouldnt be a cricital issue, it is nice to have everything correctly referenced :)
It has been fixed