Docker templates revert when docker checks for update.

I've noticed this over the last few weeks, but decide to investigate what was causing it today.

So they revert in a way where the original enviroment variables return if removed and the custom enviroment varibales are still there.

There's the duplicate container description too... have not checked what that's about.

This is the vaultwarden docker, the 3 bottom variables are not needed when the docker is managed by a database, and causes warnings in the logs, so I delete the enviroment variables.

There's other use cases that dockers wont start in certain setups... when a enviroment variable is used... so having the template be modified by an outside source seems uninteded, In some cases the original template can never match the exact users use case...

This also brings to light that I've noticed that "Fix Common Issues" plugin has a check to see if the docker template matches the original...

As much as this may seem to be helpful for new users, it just seems unnecessary. when you can delete the docker and remove the template and reinstall which would pull the current template anyway...

The template that the user modifies should never be change once the docker is installed accept for when the user modifies it from the GUI or Flash drive, or deletes it...