[#8674] fix(authz): Isolate Ranger catalog owner roles by catalog ID (#12517)

### What changes were proposed in this pull request?

Pass the stable catalog entity ID to authorization plugins and use it to
create catalog-specific Ranger owner roles.

Catalog owner roles now follow this format:

`GRAVITINO_CATALOG_OWNER_ROLE_<catalog_id>`

The chained authorization plugin also propagates the catalog ID to its
child plugins.

### Why are the changes needed?

Ranger previously used one shared `GRAVITINO_CATALOG_OWNER_ROLE` for
every catalog. As a result, the owner of one catalog could receive owner
permissions on other catalogs using the same Ranger service.

Using the stable catalog ID isolates role membership without depending
on the mutable catalog name.

Fix: #8674

### Does this PR introduce _any_ user-facing change?

Yes. Ranger creates a separate catalog owner role for each catalog using
the catalog ID as the role-name suffix.

No user-configurable property is added.

### How was this patch tested?

- Added unit tests for passing catalog IDs to authorization plugins.
- Added unit tests for generating and creating catalog-specific Ranger
owner roles.
- Updated the Ranger integration test expectation.
- Ran Spotless successfully.