Don't remove add-on conifg on add-on removal

[agners]

Proposed change

Do not remove the add-on config when the add-on gets uninstalled. The add-on config directory contains user configuration which the user might like to retain even when uninstalling the add-on. The user can easily delete the directory on his own since it is user can access the directory.

In the future we should consider adding an option at uninstall time to offer removing this directory. But meanwhile not removing it is the better default.

Type of change

• Dependency upgrade
• Bugfix (non-breaking change which fixes an issue)
• New feature (which adds functionality to the supervisor)
• Breaking change (fix/feature causing existing functionality to break)
• Code quality improvements to existing code or addition of tests

Additional information

• This PR fixes or closes issue: fixes #
• This PR is related to issue:
• Link to documentation pull request:
• Link to cli pull request:

Checklist

• The code change is tested and works locally.
• Local tests pass. Your PR cannot be merged unless tests pass
• There is no commented out code in this PR.
• I have followed the development checklist
• The code has been formatted using Black (black --fast supervisor tests)
• Tests have been added to verify that the new code works.

If API endpoints of add-on configuration are added/changed:

• Documentation added/updated for developers.home-assistant.io