fix(go): use ResolveAction() for all primitive types

[eric642]

Description here... Help the reviewer by:

• linking to an issue that includes more details
• if it's a new feature include samples of how to use the new feature
• (optional if issue link is provided) if you fixed a bug include basic bug details

Checklist (if applicable):

• PR title is following https://www.conventionalcommits.org/en/v1.0.0/
• Tested (manually, unit tested, etc.)
• Docs updated (updated docs or a docs bug required)

[eric642]

@apascal07 please review it. Enable all action types to support dynamic plugins

[apascal07]

What is your use case? We use resolve for models and embedders because they can be provided by plugins dynamically. The other types are user-defined mostly so it doesn't make sense for them to call resolve instead of look up.

[eric642]

I have a set of stateful tools, and I hope they can be re-instantiated when used by different agents. For example: agent as tool can be used for ReActAgent. In addition, our company has other prompt management platforms. We hope to be able to obtain the latest version of the prompt in real time through dynamic plugins.

[eric642]

ResolveActionFor first performs a lookup; only if the lookup fails does it proceed to search for dynamic plugins. Therefore, I believe that using ResolveActionFor does not alter the program's behavior, while still enabling dynamic plugin functionality, and it appears to present no significant issues.