Support Notebook to App in CI/CD flow

Background Sophisticated Data Scientist and Data Analyst users may want to take advantage of a CI\/CD pipeline for App Studio, allowing them to: - Provide standardized environment tags that can be used to identify the environment the app is running in (DEV, STAGING, PROD, etc.) - Run automated tests against their app - Create release branches for every build of an app - Scan their app for vulnerabilities - Deploy their app only after the previous tasks have been completed - Apply a version number to the app and communicate it to end users - Allow developers to revert to a previous release tag if bugs are found

Opportunity By giving Data Scientist and Data Analyst users the ability to integrate their data apps with their company's CI\/CD pipeline, it allows them to align their work with best practices in the software development and deployment life cycle. This may strengthen their ability to build and publish data apps autonomously within their organization. Possible Approaches - Integration (preferred): Give users an easy way within DE to connect to to and leverage existing best practice tools in the market (Github, Bitbucket, etc.). Rather than delivering these features ourselves, we make it easier for users to integrate with industry standard tools. - Abstraction (risky): Give users a way to connect to industry standard tools, but offer an opinionated and limited workflow for committing code, collaborating with others, and running a CI\/CD pipeline before deployment. - First-party (limited value, high risk): We create an internal system for managing connections to version control providers, provide hooks for CI\/CD in our deployment process, expect users to do all of their code review, merging and branching locally and sync to an external version control provider.