Network rework

[amarin-dspace]

Reworked to be able to deploy on pre-configured network infrastructure (VPC and subnets).
This is useful with customers which do not allow this to be created by dSpace personnel.
Input parameters are vpcId, the rest (subnets) can be either derived from it or use custom inputs (subnet IDs).
Nginx deployment can be limited to use specific subnets (public ones only).
@lukabudak prepared PR in parallel, #142, so all the changes in this PR can work with our qualitygate setup.
Tested to be working in both deployment scenarios (clean deployment with full admin rights and deployment with vpc already provisioned).

Terraform v1.7.1
on linux_amd64

• provider registry.terraform.io/gavinbunney/kubectl v1.14.0
• provider registry.terraform.io/hashicorp/aws v4.67.0
• provider registry.terraform.io/hashicorp/cloudinit v2.3.3
• provider registry.terraform.io/hashicorp/helm v2.13.0
• provider registry.terraform.io/hashicorp/http v3.4.2
• provider registry.terraform.io/hashicorp/kubernetes v2.29.0
• provider registry.terraform.io/hashicorp/local v2.5.1
• provider registry.terraform.io/hashicorp/null v3.2.2
• provider registry.terraform.io/hashicorp/random v3.6.0
• provider registry.terraform.io/hashicorp/time v0.11.1
• provider registry.terraform.io/hashicorp/tls v4.0.5
• provider registry.terraform.io/terraform-aws-modules/http v2.4.1

[schwichti]

Consider to use this pattern: https://gist.github.com/schwichti/cc11a6e4826fde55b999bb3b1079e4f4#create-or-read-resources

[amarin-dspace]

New requirement added: handling of only specific subnets (either via new variable or via new filtering options).
Work in progress.

[lukabudak]

Rebase your branch with main in order to apply terraform-docs changes

[amarin-dspace]

Rebase your branch with main in order to apply terraform-docs changes

Done and qualitygate already picked up the null value and commited it correctly - good work!

[lukabudak]

LGMT regarding the terraform-docs null "issue"

[schwichti]

LGTM