[FEATURE] Sensitive Data Column-Level Access Control in Non-Columnar Storage

### Describe the feature

In actual production, permission restrictions on some sensitive column fields are necessary, such as identity card numbers, phone numbers, email addresses, and other information. However, for non-column-stored data, it is necessary to read all the data stored in HDFS to form a specific piece of data, and it is not possible to intercept or shield a particular column for a user.
Currently, one possible measure is that if a user does not have the permission to access all columns, the user is not allowed to obtain any data from HDFS. However, this blanket approach prevents users from even reading ordinary non-sensitive fields.
When designing the permission system in Gravitino, is there any optimization for this situation?

### Motivation

_No response_

### Describe the solution

_No response_

### Additional context

_No response_

The issue names Gravitino's permission system and HDFS-backed non-columnar storage but provides no files, tests, entry points, proposed solution, or completion criteria. Start by locating the authorization path for non-columnar HDFS reads and determine whether column-level filtering is supported; the desired access-control behavior must be agreed before implementation.

Written by the indexing model from the issue text.