feat(py): added support for action execution context

[kirgrim]

Description:

• Added support for action execution context, to make action's callback functions more stateful and flexible

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)

[timere-nemo]

@kirgrim
I have a general question about the purpose of this context and how it will be used. The ActionExecutionContext includes a general model_config field, which is present in almost every schema. Additionally, it is unclear why certain data needs to be stored within the action itself rather than within the model. If you could provide at least one use case or example, it would help clarify this

[kirgrim]

@kirgrim I have a general question about the purpose of this context and how it will be used. The ActionExecutionContext includes a general model_config field, which is present in almost every schema. Additionally, it is unclear why certain data needs to be stored within the action itself rather than within the model. If you could provide at least one use case or example, it would help clarify this

reason is that Action is a more generic container which could store entities of different kinds, such as Model. There is no way to persist the model itself inside the registry at the moment, without using Action as a container.

Use case is for Model callback when we need to specify, for instance, output formatting based on version of the passed model data

This will be useful for Ollama and other plugins who after refactor cannot just access the global creation context