Update s4 endpoints

[mcm-mega]

Update for S4 endpoint (issue #187 ) adding:

• New S4 Endpoints: Tokyo, Paris and Barcelona
• Update old endpoints with the new domain

[Copilot]

Pull request overview

Updates the MEGA S4 Cyberduck connection profiles to reflect MEGA’s new regional endpoints and domain changes, aligning profile metadata (vendor/description/hostname/region) with the current S4 region naming scheme.

Changes:

• Updated profile Vendor, Description, and Region values to the new MEGA S4 region identifiers.
• Switched Default Hostname values from the legacy *.s4.mega.io pattern to *.megas4.com.
• Expanded/updated the selectable Regions list to include the newer MEGA S4 regions (e.g., Tokyo, Paris, Barcelona).

Reviewed changes

Copilot reviewed 4 out of 7 changed files in this pull request and generated no comments.

File	Description
MEGA S4 Tokyo.cyberduckprofile	Updates vendor/description/hostname/region to the Tokyo endpoint and refreshes the regions list.
MEGA S4 Paris.cyberduckprofile	Updates vendor/description/hostname/region to the Paris endpoint and refreshes the regions list.
MEGA S4 Montreal.cyberduckprofile	Updates vendor/description/hostname/region to the Montreal endpoint and refreshes the regions list.
MEGA S4 Amsterdam.cyberduckprofile	Updates vendor/description/hostname/region to the Amsterdam endpoint and refreshes the regions list.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[dkocher]

Can we keep the original filenames with the technical region name. Otherwise this will not update already installed profiles for users.

[mcm-mega]

The previous domain remains functional for backward compatibility, so there are no issues for already installed profiles using the old region names.
One question:
In already installed profiles, will the vendor and description also be updated automatically if we keep the original filenames?

[dkocher]

The previous domain remains functional for backward compatibility, so there are no issues for already installed profiles using the old region names. One question: In already installed profiles, will the vendor and description also be updated automatically if we keep the original filenames?

You will have to preserve the filename and the Vendor string.

[dkocher]

• Keep previous Vendor strings to allow previously configured connections to be updated with new settings
• Keep original filenames for connection profiles to allow updating previously installed versions.

[mcm-mega]

Done:

• Keep previous Vendor strings to allow previously configured connections to be updated with new settings
• Keep original filenames for connection profiles to allow updating previously installed versions.

[dkocher]

I suppose the endpoints do not support creating bucket in different regions. Therefore the Regions key should be omitted (or only include the single region name equal to Region).

[mcm-mega]

Regions removed.