OCPP 2.0.1 - Use database for storage of ChargingProfiles

[couryrr-afs]

OCPP Version

OCPP2.0.1

Describe the problem

During the development of v2.0.1 - K01 SmartCharging we followed the pattern established in v1.6 where valid profiles were stored in both an in-memory data structure and a sqlite database. After this the database is only used when the system power cycles to read the profile from the database back into memory. This was useful during the early stages of development. Looking at this now it seems to add complexity to the code to keep the two storage mechanisms in sync and duplicates data amongst memory and hdd space.

Describe your solution

Remove the in-memory data structure and read and write to the database for all operations.

Additional context

No response