Ownership Chaining: Support relation references inside views

[HarshLunagariya]

Description

This commit implements the ownership chaining support for table/view object
references inside view. The basic idea of Ownership chaining is that when
one object references another, and both have the same owner, then permissions
are only checked when the top-level object is accessed.

The scope of the current commit is to only support scenarios when parent
object is view and child objects are table/view. "[parent] view -> [child]
function" scenarios is out-of-scope for this effort.

Implementation:

• Add infrastructure changes to support ownership tracking:

  • insideView flag in RTEPermissionInfo for view context tracking
  • parentOwnerId and insideView fields in FuncExpr (for future use)
  • walk_view_rule_hook for extension-specific view rule processing and
    apply view context marking in ApplyRetrieveRule

• Add walker to traverse view definition parse trees:

  • Mark relations and functions inside views for permission checking
  • Set checkAsUser to view_owner for owned relations to enable chaining
  • Track view context using insideView flag
  • Only applies to user-defined objects created in non-shared schemas in TSQL mode

This enables proper ownership chaining behavior where tables and
views owned by the view owner can be accessed through the view.

Note: While infrastructure for function ownership chaining is included,
the actual implementation of function ownership chaining is out of scope
for this commit.

Issues Resolved

BABEL-6026

Check List

• Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is under the terms of the PostgreSQL license, and grant any person obtaining a copy of the contribution permission to relicense all or a portion of my contribution to the PostgreSQL License solely to contribute all or a portion of my contribution to the PostgreSQL open source project.

For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[tanscorpio7]

I am curious why we cannot just set the check as user to table owner when ownership chaininig is formed.

[HarshLunagariya]

This is for subsequent work where function/procedure ownership chaining will be implemented.

[tanscorpio7]

Any specific reason for including these fields in this commit ? I think bringing it along with function/procedures ownership chaining support might be preferrable for git history.