Core/vpc refactoring - Refactor vpc module to follow api/services/db layers

[dlpzx]

Feature or Bugfix

• Refactoring

Detail

Some modules under core do not completely follow the standard structure agreed for modules. In this PR I just focus on the module vpc:

• Add input validation in the api layer in the resolvers
• Create a service layer for vpc, where we check permissions and execute business logic
• The db subpackage should contain all operations on RDS. It should not contain business logic, permissions checks or input validation.

Relates

• Standardize core modules and cleanup dead code #741
• Core/Organization refactoring #989 same but for the vpc module

Security

Please answer the questions below briefly where applicable, or write N/A. Based on
OWASP 10.

• Does this PR introduce or modify any input fields or queries - this includes
  fetching data from storage outside the application (e.g. a database, an S3 bucket)?
  • Is the input sanitized?
  • What precautions are you taking before deserializing the data you consume?
  • Is injection prevented by parametrizing queries?
  • Have you ensured no eval or similar functions are used?
• Does this PR introduce any functionality or component that requires authorization?
  • How have you ensured it respects the existing AuthN/AuthZ mechanisms?
  • Are you logging failed auth attempts?
• Are you using or adding any cryptographic features?
  • Do you use a standard proven implementations?
  • Are the used keys controlled by the customer? Where are they stored?
• Are you introducing any new policies/roles/users?
  • Have you used the least-privilege principle? How?

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[dlpzx]

Testing in AWS:

• CICD pipeline succeeds
• Create network in environment
• List environment networks in Notebooks
• Delete newly create network
• Delete pre-existing network

[noah-paige]

looks good!