Is your feature request related to a problem? Please describe.
Vortex currently checks if the current user is the owner of the collection page before offering to let them edit it - if they are not the page owner, the collection is cloned instead, which detaches it from the original instance.

To empower curators in the community to work with teams, we want to be able to allow multiple users to edit the same collection, provided they have permission to do so. The backend infrastructure on the website exists for this, but the blocker to this is Vortex.

This feature would also allow staff/moderators to edit collections with Vortex.

Describe the solution you'd like
Change the way we check is the user can edit a collection from "is the user the owner of the page" to "does the user have the correct permissions to edit this collection?".

We can query this data on the Collection Graph object, with the key Permissions.

User example:

[
{
    "key": "collection:edit",
    "global": false
}
]

Staff example:

[
{
    "key": "collection:publish",
    "global": true
},
{
    "key": "collection:moderate",
    "global": true
},
{
    "key": "collection:discard",
    "global": true
},
{
    "key": "collection:view_discarded",
    "global": true
},
{
    "key": "collection:view_unlisted",
    "global": true
},
{
    "key": "collection:view_under_moderation",
    "global": true
},
{
    "key": "collection:view_draft_revisions",
    "global": true
},
{
    "key": "collection:add_tag",
    "global": true
},
{
    "key": "collection:remove_tag",
    "global": true
},
{
    "key": "collection:set_status",
    "global": true
},
{
    "key": "collection:discard_revisions",
    "global": true
},
{
    "key": "collection:edit",
    "global": true
},
{
    "key": "collection:close_bug_reports",
    "global": true
},
{
    "key": "collection:open_bug_reports",
    "global": true
}
]

Describe alternatives you've considered
n/a

Additional context
Add any other context or screenshots about the feature request here.