This adds SQL Server Notebook as a built-in extension
by pulling it from blob storage.
It also adds support in mssql extension for reading the contribution points from other extensions.
This will contribute troubleshooting and other books as widgets.
In this commit:
- Bundle the extension in the build
- Bundle in sql.sh / sql.bat so it appears in local testing
- Avoid installing in Stable. Should only appear in Dev/Insiders builds
- Extensions with `notebook.books` contribution point will be discovered & their books available in MSSQL
Coming later:
- Integrate this with Maddy's work to show a Notebooks widget in the SQL Server big data cluster UI
- When clause isn't supported yet for filtering. Will be done as we refactor towards more books for different server types
* Add test for opening existing SQL file and typing text into it
* Clean up
* More cleanup, remove unneeded queryEditor and add smoke test scripts
* Update comments to be clearer
* First version of Stress - moving over from feat/Stress1 branch
* a working version - still issues with stresssified notebook tests
* update notebooks to use new message event (#5395)
* Latest changes for notebook tests
* Stressify objectExplorer tests
* formatting changes
* removing the tracing added previously and ability to set tsc verbose option in tsconfig.json
* addressing review feedback
* addressing review feedback
* implementing runtime parameter for Stress
* addresing review feedback and moved out stress modules to its own project outside of azuredata source tree
* referencing adstest from the github location
* incorporating review feedback
* Review feedbak
* removing uncommong entries added to .gitignore
* removing unrelated change
* replacing debug/trace statements with console.info or cosole.warn statments in integration-tests\main.tx
* Update vscode dependency (needed for test runner) to pull latest 1.x version
* Update to use 1.1.5 instead
* Undo change to vscode engine version
* Switch to using vscodetestcover for running tests
* Switch to cobertura output for coverage reports
* Remove vscode dependency from profiler extension
* Update yarn.lock with combined changes
* automate the setup and use akv to store values
* update readme.md
* get rid of the save to file part
* update readme
* add more messages
* fix the error
* fix some errors
* fix the readme
* runAllCells API
* add comment
* more run cells fixes
* Add integration test
* Add multiple cell SQL notebook test
* Comment out python tests as they fail in the lab
* remove unused imports
* PR comments
* Remove localize
* Return true instead of promise.resolve(true)
