Notify consumer about charging profile update when a transaction stops

[Pietfried]

Describe your changes

This PR adds executing signal_set_charging_profiles_callback when a transaction is stopped to notify the consumer. The stopped transaction might have removed previously reported TxProfiles (as part of the composite schedule) which could influence the load balancing / charging power of the EVSEs.

Remark: Looking at how the signal_set_charging_profiles_callback and also set_charging_profiles_callback (of ocpp201) I would suggest to change the name of these variables to better represent their purpose. A libocpp user should get notified in case profiles are added / removed which leads to a change of the composite schedule. This can happen when charging profiles are added by SetChargingProfile.req but also when transactions stop (because TxProfiles) might be removed. A more appropriate name would e.g. be charging_profiles_updated_callback.

I covered that in this issue.

Issue ticket number and link

Checklist before requesting a review

• I have performed a self-review of my code
• I have made corresponding changes to the documentation
• If OCPP 2.0.1: I have updated the OCPP 2.0.1 status document
• I read the contribution documentation and made sure that my changes meet its requirements

[maaikez]

It would be nice if the callback was called only when the charging profile is indeed changed. You said you would make a ticket for it, so for now it's ok I think.

[maaikez]

looks good.