PGOV-314: Setup for deployment

[acabouet]

This PR adds configuration and scripts for deploying the Drupal backend and the NextJS frontend of the PGOV MVP to the Cloud.gov environment using cloudfoundry cli.

In summary:

• manifest.yml is cloud.gov environment settings including the buildpacks we will use to build the frontend and backend.
• .bp-config is config for the PHP, NGINX, and apt (for dependency install) build packs
• bootstrap.sh is the script to install the drupal site, import existing config, optionally import a database, and complete migrations for files and media.
• bin/deploy-cloudgov.sh is a script that automates the creation of the services need for the backend to run (database, storage, secrets), setting necessary environment variables to pass to drupal install on the server, and then running the bootstrap script.
• cronish.sh sets up automated cron

Additionally in this PR is config to enable api connections between the dev environment frontend and backend, and a content security policy for the frontend that allow images from drupal and frontend app preview in drupal to work.

Misc other stuff happening in here: labels added to admin menu for gin theme, removing a field that no longer exists on agencies from requests and templates on the frontend. Also .github/workflows/cloudfoundry-deploy.yml is the start of the config that will allow for automated building, testing, and deployment of new PRs.

[dgading]

The frontend code and what I know of the config looks good. I think I have some fixes for the facets on the goal search in my PR. I am not very familiar with the devops part so I am not sure what I am looking at to approve.

[vauxia]

Oof, this is pretty low. It might be OK, but if we're seeing issues with migrations etc, I'd look here first.

[acabouet]

The migrations with issues are failing because of a timeout of 180 seconds for build operations run via the cloudfoundry CLI. The migrations that complete within three minutes like agencies and goals finish without issues. The ones that take longer like plan_files and report_files fail due to timeout. The timeout maximum is unfortunately not impacted by this setting and I think we need to get with cloud.gov support to change. Will reach out to them.

64M is the minimum php memory requirement for Drupal 10 so 512M seemed generous but definitely down to bump this up if we're seeing other issues.