vscode: Don't show extension recommendations for common .env file extensions

Steps to Reproduce: Open a .env.local, .env.production, .env.example, or .env.development file.

Actual: Keeps prompting for each new .env file extension. Search results are not useful.

Extension search for a production file:

Expected: Just edit the file plainly. It doesn’t need much to write env files.

About this issue

I am glad we are bringing comedy gold.

@sandy081 can we look at the contributes.language field in the package.json? Or we do not have this info at this moment?

I do not think this will help. The root problem here is to come up with proper non generic tags to search in MP.