feat: create `default` VPC network if it does not exist already

[lvaylet]

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

• [X] Make sure to open an issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
• [X] Your change follows guidelines in the Contributor guide
• [ ] Communicate test infrastructure changes, i.e. API enablement, secrets
• [ ] Appropriate docs were updated (if necessary)

🛠️ Fixes #1043

[conventional-commit-lint-gcf[bot]]

🤖 I detect that the PR title and the commit message differ and there's only one commit. To use the PR title for the commit history, you can use Github's automerge feature with squashing, or use automerge label. Good luck human!

-- conventional-commit-lint bot https://conventionalcommits.org/

[lvaylet]

Hi @minherz, any chance you could review this PR for milestone/0.10?

[minherz]

updated: This change is rolled back. The rationale behind the rollback includes:

• COB deprecates support for provisioning demo applications in order to focus on demonstration of the observability features of Cloud Ops services. The expectations for the default VPC configuration exists in the provided project is reasonable and works like this in majority of deployments.
• Provisioning a new VPC on the user's project may have unexpected side-effects on other workflows running in the project
• The implemented provisioning lacks dependencies which results in unstable deployment and multiple failures due to unresolved dependencies.

[lvaylet]

Thanks for the update. I just tested this approach in a clean project with no default VPC. It does not work indeed. I was pretty sure I had tested it prior to submitting the PR. I probably did so in a project that already had a default VPC.