Single tech/databricks ops yuheng

[yuhenghub]

Type of PR

• Code changes
• Test changes

Purpose

1. Add following files and code following the general readme file ├── multi-notebooks │   ├── notebooks │   │ ├── main_notebook.py │   │ ├── module_a_notebook.py │   │ └── module_b_notebook.py │   └── tests │   └── integration │   ├── main_notebook_test.py │  ├── module_a_test.py │  └── module_b_test.py

2. Module introduction: Leverage Lace's idea on double price sample

   • module_a_notebook: Python Code with Dataframe to double price tested by module_a_test
   • module_b_notebook: PySQL Code with SQL Table to double price tested by module_b_test
   • main_notebook: calling the module_a_notebook and module_b_notebook and being tested by main_notebook_test

Does this introduce a breaking change? If yes, details on what can break

No

Author pre-publish checklist

• [X] Added test to prove my fix is effective or new feature works
• [X] No PII in logs
• [X] Made corresponding changes to the documentation

Validation steps

• Run test notebooks in tests folder in Databricks and later in Azure DevOps pipeline

Issues Closed or Referenced

• References #329