cli-pipelines template: remove project directory (#3294)

## Changes
Remove project_pipelines directory and bubble up subdirectories.
Consolidated 2 READMEs to have only 1 in the directory.

## Why
For one pipeline, the transformations, explorations, and utilities
folders will be in the root of the my_project directory.

## Tests
Updated acceptance test output.

Author: alyssa-db

acceptance/pipelines/init/error-cases/output/my_project/README.md

@@ -20,6 +20,23 @@ The 'my_project' project was generated by using the CLI Pipelines template.
    https://docs.databricks.com/dev-tools/vscode-ext.html. Or the PyCharm plugin from
    https://www.databricks.com/blog/announcing-pycharm-integration-databricks.
 
+## Pipeline Structure
+
+This folder defines all source code for the my_project_pipeline pipeline:
+
+- `explorations`: Ad-hoc notebooks used to explore the data processed by this pipeline.
+- `transformations`: All dataset definitions and transformations.
+- `utilities` (optional): Utility functions and Python modules used in this pipeline.
+
+## Getting Started
+
+To get started, go to the `transformations` folder -- most of the relevant source code lives there:
+
+* By convention, every dataset under `transformations` is in a separate file.
+* Take a look at the sample under "sample_trips_my_project.py" to get familiar with the syntax.
+  Read more about the syntax at https://docs.databricks.com/dlt/python-ref.html.
+
+For more tutorials and reference material, see https://docs.databricks.com/dlt.
 
 ## Deploying pipelines
 

acceptance/pipelines/init/error-cases/output/my_project/databricks.yml

@@ -7,7 +7,7 @@ bundle:
 include:
   - resources/*.yml
   - resources/*/*.yml
-  - my_project_pipeline/*.yml
+  - ./*.yml
 
 # Variable declarations. These variables are assigned in the dev/prod targets below.
 variables:

…ne/explorations/sample_exploration.ipynb …ct/explorations/sample_exploration.ipynbacceptance/pipelines/init/error-cases/output/my_project/my_project_pipeline/explorations/sample_exploration.ipynb renamed to acceptance/pipelines/init/error-cases/output/my_project/explorations/sample_exploration.ipynb acceptance/pipelines/init/error-cases/output/my_project/my_project_pipeline/explorations/sample_exploration.ipynb renamed to acceptance/pipelines/init/error-cases/output/my_project/explorations/sample_exploration.ipynb

@@ -20,6 +20,23 @@ The 'my_python_project' project was generated by using the CLI Pipelines templat
    https://docs.databricks.com/dev-tools/vscode-ext.html. Or the PyCharm plugin from
    https://www.databricks.com/blog/announcing-pycharm-integration-databricks.
 
+## Pipeline Structure
+
+This folder defines all source code for the my_python_project_pipeline pipeline:
+
+- `explorations`: Ad-hoc notebooks used to explore the data processed by this pipeline.
+- `transformations`: All dataset definitions and transformations.
+- `utilities` (optional): Utility functions and Python modules used in this pipeline.
+
+## Getting Started
+
+To get started, go to the `transformations` folder -- most of the relevant source code lives there:
+
+* By convention, every dataset under `transformations` is in a separate file.
+* Take a look at the sample under "sample_trips_my_python_project.py" to get familiar with the syntax.
+  Read more about the syntax at https://docs.databricks.com/dlt/python-ref.html.
+
+For more tutorials and reference material, see https://docs.databricks.com/dlt.
 
 ## Deploying pipelines
 

…project_pipeline/my_project.pipeline.yml …utput/my_project/my_project.pipeline.ymlacceptance/pipelines/init/error-cases/output/my_project/my_project_pipeline/my_project.pipeline.yml renamed to acceptance/pipelines/init/error-cases/output/my_project/my_project.pipeline.yml acceptance/pipelines/init/error-cases/output/my_project/my_project_pipeline/my_project.pipeline.yml renamed to acceptance/pipelines/init/error-cases/output/my_project/my_project.pipeline.yml

@@ -7,7 +7,7 @@ bundle:
 include:
   - resources/*.yml
   - resources/*/*.yml
-  - my_python_project_pipeline/*.yml
+  - ./*.yml
 
 # Variable declarations. These variables are assigned in the dev/prod targets below.
 variables: