[Improvement] Rethinking the implement of partition operations

[FANNG1]

What would you like to be improved?

The current partition operation is out of dispatcher, leading to some issues:

1. [FEATURE] Provide specific classLoader for Partition operation #2997
2. blocks [#2780] Improvement(server,core): Move tree lock from rest api to the corresponding implementation to minimize tree lock range. #2873
3. makes event listener hard to inject to partition operations.

                  Table loadTable = dispatcher.loadTable(tableIdent);
                  Partition p = loadTable.supportPartitions().getPartition(partition);
                  return Utils.ok(new PartitionResponse(DTOConverters.toDTO(p)));
```to 

[FANNG1]

cc @jerryshao @mchades @yuqi1129

[jerryshao]

@mchades please take a look.

[jerryshao]

I think it is necessary to refactor this part, we have to carefully rethink the whole thing.

BTW, I'm curious why Hive's partition operation doesn't have such problem like #2997 mentioned.

[FANNG1]

I think it is necessary to refactor this part, we have to carefully rethink the whole thing.

BTW, I'm curious why Hive's partition operation doesn't have such problem like #2997 mentioned.

I guess Hive partition operations doesn't invoke the DynConstructor to load a new class. cc @TEOTEO520

[yuqi1129]

I think it is necessary to refactor this part, we have to carefully rethink the whole thing.

BTW, I'm curious why Hive's partition operation doesn't have such problem like #2997 mentioned.

It's because the classDynConstructors that Hive catalog use is our class NOT class provided by Iceberg

please see: "com.datastrato.gravitino.catalog.hive.dyn.DynConstructors"