smart charging: updated validation to be explicit when conforming profile

[Pietfried]

Original PR reopened: #815

Describe your changes

As part of the validation there are times, per the standard, that a profile needs to be modified to conform to the spec. During the initial pass we had this logic in validate methods and did not explicitly state that the modification was occurring.

• renamed validate_profile to conform_and_validate_profile in order to convey the potential for change.
• renamed validate_and_add_profile to conform_validate_and_add_profile in order to convey the potential for change.
• added method conform_validity_periods to better show where the change is occurring.
• added comment as to why the conform is being performed.
• added logging to show the values that are being set.
• added a new conform_schedule_number_phases function moving existing modification of the number of phases.
• updated some methods to use const on profiles where attributes are not being modified.

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