DISCUSSSION Draft / publish workflow for collective pages (with versioned snapshots)

Is your feature request related to a problem? Please describe.
=> Make some pages of your collectives Public available to the instance or managed by the admin

I have re-read #666, and I believe there is now more and more argument to do this.
While a public link is nice you need to copy this link somewhere...
You end up with a list of links to manage.
It would be much cleaner to publish to the instance in preview mode some pages.
This would remove tracking this list to other users.

So publish would be a share link but visible in the collectives' app by other users of Nextcloud.
Of course this new option could be disabled by the admin to make sure that collectives cannot be published in some cases.

Describe the solution you'd like
=> Publish this page create a page accessible to the instance
=> there is a little indicator on the page list to show that it is published 🌐
=> When you are in edit mode there is warning to tell you that this page is published to the instance.

Describe alternatives you've considered
=> A similar solution to the tables app => Publish as an app some collectives.

Additional context
Do a proper landing page where people could subscribe to the collectives.

Start by reviewing the existing page-sharing flow and the tables app alternative referenced in the issue, then clarify how instance visibility, admin control, previews, indicators, warnings, and versioned snapshots should interact. Done means the scope and acceptance criteria are agreed for publishing collective pages, including the optional landing-page or subscription behavior.