Fix cloud resource quota in testbed prerequisites

[ideaship]

The documented minimum project quota for volumes, volume storage, security group rules, and ports did not match the actual resource usage observed after deployment.

Volumes: 7 base volumes (80 GB each) + 9 data volumes (20 GB each) = 16 volumes using 740 GB, not 18 volumes using 360 GB.

Security group rules: Terraform creates 9 rules. Each of the 3 security groups (2 Terraform-managed + 1 default) gets 2 auto-created egress rules = 6. The default group also has 2 auto-created ingress rules. 9 + 6 + 2 = 17 total, not 16.

Ports: 7 instance ports + 1 router interface + 1 distributed/HA port = 9 total, not 6.

AI-assisted: Claude Code

[github-actions]

✅MegaLinter analysis: Success

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ ACTION	actionlint	3		0	0	0.03s
✅ JSON	jsonlint	4		0	0	0.09s
✅ JSON	prettier	4		0	0	0.51s
✅ JSON	v8r	4		0	0	9.85s
✅ MARKDOWN	markdownlint	155		0	0	2.14s
✅ MARKDOWN	markdown-table-formatter	155		0	0	0.34s
✅ REPOSITORY	checkov	yes		no	no	16.41s
✅ REPOSITORY	git_diff	yes		no	no	0.04s
✅ REPOSITORY	secretlint	yes		no	no	1.62s
✅ REPOSITORY	trufflehog	yes		no	no	3.97s
✅ SPELL	codespell	163		0	0	0.44s
✅ SPELL	lychee	163		0	0	16.11s
✅ YAML	prettier	4		0	0	0.36s
✅ YAML	v8r	4		0	0	4.73s
✅ YAML	yamllint	4		0	0	0.43s

See detailed reports in MegaLinter artifacts

Your project could benefit from a custom flavor, which would allow you to run only the linters you need, and thus improve runtime performances. (Skip this info by defining FLAVOR_SUGGESTIONS: false)

• Documentation: Custom Flavors
• Command: npx mega-linter-runner@9.4.0 --custom-flavor-setup --custom-flavor-linters ACTION_ACTIONLINT,JSON_JSONLINT,JSON_V8R,JSON_PRETTIER,MARKDOWN_MARKDOWNLINT,MARKDOWN_MARKDOWN_TABLE_FORMATTER,REPOSITORY_CHECKOV,REPOSITORY_GIT_DIFF,REPOSITORY_SECRETLINT,REPOSITORY_TRUFFLEHOG,SPELL_LYCHEE,SPELL_CODESPELL,YAML_PRETTIER,YAML_YAMLLINT,YAML_V8R

Show us your support by starring ⭐ the repository