Exclude *.map files from shipped extension

Extension Version: 2020.8.109390

I was looking into why Python was taking a little while to download on my machine. From a quick investigation, it looks like the datascience-ui folder in the shipped extension contains three large .map files:

du -ah . | sort -rh | grep '\.map'

14M	./out/client/extension.js.map.disabled
7.1M	./out/datascience-ui/notebook/commons.initial.bundle.js.map
3.4M	./out/datascience-ui/viewers/commons.initial.bundle.js.map
216K	./out/datascience-ui/notebook/nativeEditor.js.map
128K	./out/datascience-ui/notebook/interactiveWindow.js.map
8.0K	./out/datascience-ui/viewers/plotViewer.js.map
8.0K	./out/datascience-ui/viewers/dataExplorer.js.map

These should usually be excluded as they are only needed during development

[rchiodo]

No I don’t think so. We only need them when debugging, not when getting logs from users.

[luabud]

We should:

• Remove the map files from the vsix
• Remove the setting (python.diagnostics.sourceMapEnabled)
• Update our issue documentation to stop asking people to use the setting
• Generate source map during build (and save them along the relesed vsix)

If we need this for debugging, we can give users a link to the map files and instructions as to how to put it on the right place, so we get the info we need