docs: Remove stale custom-hosting deployment guides

[Zfinix]

As of Serverpod 3.5+, serverpod create no longer generates the deploy/ folder that the GCE Terraform, GCR Console, and AWS EC2 Terraform guides depend on (see serverpod/serverpod#4703). Following these guides today leaves users without the script files they reference.

Removed:

• 02-google-cloud-engine-terraform.md
• 03-google-cloud-run-console.md
• 04-aws-ec2-terraform.md

Also:

• Renumbered 05-hosting-elsewhere.md to 02- and 06-community-supported.md to 03- to close the gap.
• Updated 01-choosing-a-strategy.md: dropped the three deleted bullets from the "Pick a guide" list and the now-inaccurate "the following pages walk through each path" clause.
• Added description frontmatter to the two surviving pages.
• Trimmed a noise-pattern preamble sentence on 02-hosting-elsewhere.md.

No external pages linked to the deleted slugs. The only inbound reference (01-choosing-a-strategy.md's "Pick a guide" list) was updated in this PR.

Closes #564

Related: serverpod/serverpod#4703

[developerjamiu]

LGTM.

This looks like losing some valuable information to the community though there's not much we can do about it. I think one thing we can do is have a todo to repurpose some of these pages to hold a list of well tested articles written by community members on how to deploy to other platforms.

[Zfinix]

LGTM.

This looks like losing some valuable information to the community though there's not much we can do about it. I think one thing we can do is have a todo to repurpose some of these pages to hold a list of well tested articles written by community members on how to deploy to other platforms.

Yes it is some valuable information lost, and yes i think we need deployment docs to AWS, GCP, Railway etc, it would make development a breeze, but the docs in its current state is fundamentally broken as the /deploy folder and all its files don't ship with new projectes anymore so Im not sure, maybe we can create an issue for this @Swiftaxe.

[Swiftaxe]

These guides still exist under older versions, so the information is not completely lost. They are outdated, though, and should not ship with the latest docs.

I will create an issue to address this with a better solution.