Support setting a vanity URL when publishing to Connect #4474

Summary

Publisher can set a vanity URL only for Connect Cloud deployments. For Connect (on-prem) deployments, Publisher has no option to set one. Users must set the vanity URL in the Connect dashboard or through the API after the first deploy.

Current behavior

• The configuration schema has vanity_name only in the [connect_cloud] section. The [connect] section has no vanity field.
• The Connect API client in packages/connect-api does not call the vanity endpoint.
• The extension still defines a publish/setVanityURL event label and a log formatter, but no code sends this event. This code is left over from the old Go backend.

Proposed behavior

1. Add an optional vanity_url key to the [connect] section of the configuration, for example vanity_url = "/my-app/".
2. If the key has a value, Publisher calls PUT /v1/content/{guid}/vanity after a successful deploy.
3. Publisher shows a "Set Vanity URL" step in the deploy log, with the existing publish/setVanityURL event.
4. If Connect rejects the path, Publisher shows a clear message. For example, the path conflicts with another vanity URL, the path is reserved, or the user does not have permission to set vanity URLs.