Removing the UseTaskFriendlySynchronizationContext key on uninstall breaks other modules

[ghost]

Removing the aspnet:UseTaskFriendlySynchronizationContext key from the web.config on module uninstall breaks other modules installed on my DNN site that require the use of the key.

Can we just add the key on install if it's not already present in the web.config and then not remove it on uninstall. As there's no way to tell if it was already present / if anything else uses the key.

[WillStrohl]

Honestly, I rarely see this key ever used. What other modules do you see using this?

[StevenFisherCantarus]

We have used this key in several modules across several clients, its true that it is used rarely and would only cause a problem if PolyDeploy was uninstalled, however I think we should leave the key there by default.

[Swimburger]

Since the installation instructions tell you to add the key yourself, I think it makes sense to remove it yourself too. Maybe there should be an uninstall guide along with the install guide.