Rename v201 to v2 for OCPP modules

[Pietfried]

Describe your changes

This PR addresses the renaming changes in libocpp from v201 to v2 / V201 to V2. All occurances have been renamed according to the changes in libocpp.

Issue ticket number and link

Companion PR in libocpp

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• I read the contribution documentation and made sure that my changes meet its requirements

[maaikez]

Looks good.

Do you want to also change the name of the module? OCPP2 instead of OCPP201?

I am missing python changes though, but I think that's on purpose. So in the python tests we still have ChargePoint201, charge_point_v201, ocpp.v201, call201, call_result201, GenericOCPP201ConfigAdjustment, OCPP201ConfigVariableIdentifier, validate_status_notification_201, TestOcpp201CostAndPrice, etc.
But changes in tests also has effect on everest utils probably.

[Pietfried]

Looks good.

Do you want to also change the name of the module? OCPP2 instead of OCPP201?

I am missing python changes though, but I think that's on purpose. So in the python tests we still have ChargePoint201, charge_point_v201, ocpp.v201, call201, call_result201, GenericOCPP201ConfigAdjustment, OCPP201ConfigVariableIdentifier, validate_status_notification_201, TestOcpp201CostAndPrice, etc. But changes in tests also has effect on everest utils probably.

Yes those are left out on purpose for now.

I would not rename the module now since this breaks existing configuration. We can discuss this at a later point.

[SebaLukas]

👍