Re-flash `FRP` on new installation

It has been reported to be common for ROMs to always re-flash FRP upon installation in order to avoid the situation where a previously used Google account on the prior installation would trigger FRP causing issues for the new installation as noted in this thread: https://community.iode.tech/t/cant-unlock-eom-anymore-because-frp-is-not-flashed-ive-been-told/7282/9

Now the actual issue is iodé not flashing the FRP partition. There’s no reason to keep a Google account in FRP, there’s no mechanism to disable it from microG, it serves no purpose on a phone without Play Services, other than create a potential brick risk.

One FP5 user with this problem was able to re-flash stock FPOS which in turn reset the FRP flag, then they proceeded to install iodé again: https://community.iode.tech/t/can-not-uncheck-oem-unlocking-fp5/6818. One of the first clues they had triggered FRP was that they could not disable "Allow OEM Unlocking".

But in the case of the FP4 user from the first link, they had also manually run fastboot flashing lock_critical and then when realizing FRP was active and they needed to reflash stock to reset it, they realized that they could not re-enabled "Allow OEM Unlocking" (it would not "stick") so they are stuck likely needing to send the phone back to Fairphone for reflashing.