removed Notebook creation from extension since it is moving to built-in

[amunger]

Fixes #9250

This should be merged in coordination with microsoft/vscode#144789 to limit the amount of time that the command is unavailable/duplicated.

The create Notebook flow is still used pretty widely in the test framework, so this change does not completely remove it.

This will remove the functionality of registered 3rd party notebooks appearing in the "Create Jupyter Notebook" quick pick menu since that command will simply create a Python Notebook.

• Pull request represents a single change (i.e. not fixing disparate/unrelated things in a single PR).
• Title summarizes what is changing.
• Has a news entry file (remember to thank yourself!).
• Appropriate comments and documentation strings in the code.
• Has sufficient logging.
• Has telemetry for enhancements.
• Unit tests & system/integration tests are added/updated.
• Test plan is updated as appropriate.
• package-lock.json has been regenerated by running npm install (if dependencies have changed).

[DonJayamanne]

"Create Jupyter Notebook" quick pick menu since that command will simply create a Python Notebook.

Thats not true, if you open a julia notebook and use that, then the new notebook created using that command defaults to Julia.
Similarly if you are an R user, the new notebook defaults to R & not python.

[amunger]

the new notebook defaults to R & not python

That happens through controller selection for the created notebook, not the notebook creation itself. This change should not affect that behavior, although I'm having a hard time testing that in OSS.

[DonJayamanne]

Thats not true, if you open a julia notebook and use that, then the new notebo

Yeah looking at the old code, it never worked, looks like the code was lost at some point.
Surprised no one is complaining, I guess it works because untitled notebooks automatically have their kernel change to what they used last, and that results in cell languages getting updated.

[codecov-commenter]

Codecov Report

Merging #9311 (48a4e41) into main (f03d91f) will increase coverage by 0%.
The diff coverage is n/a.

❗ Current head 48a4e41 differs from pull request most recent head 4d497be. Consider uploading reports for the commit 4d497be to get more accurate results

@@          Coverage Diff          @@
##            main   #9311   +/-   ##
=====================================
  Coverage     74%     74%           
=====================================
  Files        219     219           
  Lines      10919   10919           
  Branches    1512    1512           
=====================================
+ Hits        8153    8183   +30     
+ Misses      2176    2138   -38     
- Partials     590     598    +8     

Impacted Files	Coverage Δ
src/client/datascience/dataScienceSurveyBanner.ts	69% <0%> (-7%)	⬇️
src/client/common/process/pythonDaemonPool.ts	76% <0%> (+1%)	⬆️
...ent/datascience/progress/kernelProgressReporter.ts	80% <0%> (+2%)	⬆️
src/client/common/process/proc.ts	78% <0%> (+2%)	⬆️
.../client/datascience/plotting/plotViewerProvider.ts	41% <0%> (+2%)	⬆️
src/client/common/featureDeprecationManager.ts	37% <0%> (+3%)	⬆️
src/client/extension.ts	61% <0%> (+3%)	⬆️
src/client/datascience/multiplexingDebugService.ts	55% <0%> (+3%)	⬆️
src/client/datascience/datascience.ts	95% <0%> (+4%)	⬆️
...ient/datascience/data-viewing/dataViewerFactory.ts	87% <0%> (+4%)	⬆️
... and 3 more

[DonJayamanne]

We must change the engine in package.json (to 1.65-insider) to ensure this change goes out ONLY with the corresponding 1.65 version of VS Code.