Settings: add way to disable different modules/features

[JadenSimon]

It'd be nice if we could disable features if we feel that they aren't important for our workflows and/or don't work correctly because of lack of permissions. AWS has many different services for tons of different uses, so allowing the user to customize their experience just makes sense.

Having this configurable per-profile would be a huge plus, though a global solution could be acceptable if it's easy to manage.

Related:

• SAM CLI detection: "Don't show again" if SAM CLI is not found #1244
• Request ability to suppress credential notification popup #1433
• "Add Debug Configuration" codelens polluting python import statements #1585
• Support minimum-trust workspace #1823

[justinmk3]

Most of the related issues (thanks for gathering them) are cases where configuration would be a misfeature, and instead we should just do the Right Thing.

So we need a clear motivation and scope. If the scope is to show/hide services in AWS Explorer, that seems reasonable and extends existing functionality in the Resources node.

For cases like SAM CLI support, making that support configurable puts the burden on the customer to decide when/if they need it. Instead, Toolkit's support of SAM CLI should be unobtrusive and low-cost so that having it enabled does not require a customer choice.

[JadenSimon]

So we need a clear motivation and scope. If the scope is to show/hide services in AWS Explorer, that seems reasonable and extends existing functionality in the Resources node.

I was thinking more along the lines of hiding services, though some features do deserve their own toggles if they're too in-your-face. It's more about keeping things lean which also means not making everything configurable.