Misleading option to remove SSID

[ghalse]

CAT has long had a configuration option to allow organisational administrators to request the removal of SSIDs. This is useful for removing legacy or provisioning networks.

Unfortunately with the push towards geteduroam, this doesn't necessarily work any more (see #190). The existence of the option is therefore somewhat misleading, since it only works if you use the apps downloaded from CAT (and then not necessarily all apps, since those that rely on eapconfig won't).

I think we either need to fix things so this works in the geteduroam app (first prize); clearly document the limitations, visible from the UI; or remove the option altogether.

[twoln]

Removing it at this stage would be the a hard decision, I think. There are 131 profiles that use this option. We need to talk to geteduroam about this.

[restena-sw]

It would certainly be appropriate to explain that this option only works where it does. Other options in CAT have this blue "Question mark bubble" where you can click and get more info (e.g. custom SSID). It would be very easy to add this: https://github.com/GEANT/CAT/blob/master/web/lib/admin/OptionDisplay.php#L244

The first prize is however really hard. Many OSes do not allow to remove SSIDs that the provisioning app did not configure by itself. This is true at least for Android and iOS / macOS. We worked around that with CAT installers by "provisioning" that to-be-removed SSID as a "connect only manually, WPA-PSK, no PSK configured" which essentially makes the SSID lowest priority. But even that was a hack on not necessarily a role model to follow.