Merge latest changes from Lincomatic V8.2.1 > V8.2.3

[glynhudson]

• PP_AUTO_AMPACITY changes
• AutoSetCurrentCapacity() should set a max current capacity not actual charge current. lincomatic/open_evse#156
  -> used to change current capacity to PP ampacity. now, only change it
  if currently higher than PP ampacity
  -> GetMaxCurrentCapacity() is limited to PP ampacity in STATE B/C

20230206 SCL

• added BOOTLOCK - when defined, EVSE locked until receives $SB
• OpenEVSE start a session when there is no ESP connected lincomatic/open_evse#154
• Requires WiFi FW V4.2.1 or higher

20220408 V8.2.1 SCL

• fix bug: SaveSettings() should save GetMaxCurrentCapacity() instead of GetCurrentCapacity(), in case called during throttling

[glynhudson]

@jeremypoulter please could you help with merging these latest changes from Lincomatic. Should this PR be targeting stable? The version numbers are out of sync hence the need to release this under V8.2.3

@KipK could you advise what build flags features we can now disable since these features are handled in UI V2 e.g energy countes, limits etc

[KipK]

I'm not home for few days , but needs something like PP_AUTOAMPACITY ( as before ) for eu builds and BOOTLOCK for all builds ( needs wifi fw > 4.1.7 )

[lincomatic]

I cannot change the platformio.ini to fit users' specific needs. Sorry. OpenEVSE needs to use their own platformio.ini

[KipK]

That's already the case on openEvse git. Those flags should be added there.

[jeremypoulter]

@glynhudson Looks good to me, both repos now use master as the main/stable branch now. This means GitHub tracks the differences between the two repos better

[KipK]

@glynhudson , I don't have it under my eyes now but the flags we can disable are the one for limits and timers. I would keep energy meter even if handled by ESP32 now and remove it later ( needs to keep the amp sampling but remove the counter part ) .
I think RAPI_WF can be disabled too and perhaps some other older stuff.

[KipK]

@glynhudson
so here are my compile flags here :
Is rapi_wf really used ? It's supposed to enable AP mode when pressing the front button, not sure this is really safe as default ^^

build_flags =
-D OEV6
-D RELAY_PWM
-D SHOW_DISABLED_TESTS
-D AMMETER
-D RAPI
-D RAPI_SERIAL
#-D RAPI_WF
-D RAPI_BTN
#-D TIME_LIMIT
#-D CHARGE_LIMIT
-D MENNEKES_LOCK ( not sure it has sense to enable this by default ? )
-D DELAYTIMER
-D RTC (
-D BOOTLOCK

And no change for the emonevse but only need one now, no threephase needed:

[env:emonevse]
extends = env:openevse
build_src_flags=
  ${common.eu_build_flags}
  -D PP_AUTO_AMPACITY
  -D 'VERSION="${common.version}.T2"'

BOOTLOCK enabled will need to mention this firmware needs next release wifi fw version ( 4.1.7 won't unlock the evse )

[KipK]

I've remade the PR with solved conflicts #19