introduce logic for providing lineage ownership information

[dechoma]

Describe your changes:

Fixes #17406

This change introduces the concept of lineage ownership in the context of the lineage API.
The user who is the owner of a lineage destination entity becomes the owner of the direct upstream lineage information.
Thanks to this change, the IsOwner() condition can be used to create lineage RBAC policies.

Type of change:

• Bug fix
• Improvement
• New feature
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation

Checklist:

• I have read the CONTRIBUTING document.
• My PR title is Fixes <issue-number>: <short explanation>
• I have commented on my code, particularly in hard-to-understand areas.
• For JSON Schema changes: I updated the migration scripts or explained why it is not needed.

[github-actions]

Hi there 👋 Thanks for your contribution!

The OpenMetadata team will review the PR shortly! Once it has been labeled as safe to test, the CI workflows
will start executing and we'll be able to make sure everything is working as expected.

Let us know if you need any help!

[dechoma]

continuation in #17661