Ownership module to accept different scopes

What does this MR do and why?

Try a shared ownership method to untangle some technical debt and hidden "direct-owners-only" logic gotchas.

At the moment, there's no distinction between "has owner role" and "directly owned by". This attempts to create a clear method that can be used for more calls to owned_by to determine what these calls actually intend.

Split off MRs

• Update `owners` method and add `direct_owners` ... (!92871 - closed)

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Related to #365459