[api] Introduce Hierarchical ResourceName for Resource Creation

[GreatEugenius]

Linked issue: #469

Purpose of change

Introduce Hierarchical ResourceClassName for Cross-Language Resource Creation

Tests

E2E test

API

Yes, use ResourceName to replace Constant.

Documentation

• doc-needed
• doc-not-needed
• doc-included

[GreatEugenius]

Hi @xintongsong, could you please confirm the order of ResourceName hierarchy first? I will commit to the document and implement the Python side once the order is finalized.

[xintongsong]

This might be more like a personal opinion, but I'd prefer ResourceName.ChatModel.ANTHROPIC_CONNECTION over ResourceName.ChatModel.Anthropic.CONNECTION.

Imagine typing this in an IDE, when you type ANT, you'll see a list of only two options ANTHROPIC_CONNECTION and ANTHROPIC_SETUP, and you can easily select between them. Having to first select Anthropic, then type another dot to show the list of CONNECTION and SETUP just makes things more complicate.

On the other hand, without this change, when you type OLL, you'll see a list of OLLAMA_CHAT_MODEL_CONNECTION, OLLAMA_CHAT_MODEL_SETUP, OLLAMA_EMBEDDING_MODEL_CONNECTION, OLLAMA_EMBEDDING_MODEL_SETUP and potentially more if we support more resource types in future. First narrowing down to ChatModel should be helpful significantly reduce the options in the list.

[xintongsong]

And for the python wrapper, I'd suggest ResourceName.ChatModel.PYTHON_WRAPPER_CONNECTION and ResourceName.ChatModel.PYTHON_WRAPPER_SETUP, to make it more explicit that this is a wrapper rather than a normal resource provider. The infix _WRAPPER_ doesn't really add any operational cost, but would be more readable.