Updated plugin documentation with hooking mechanism overview

[bjeffries]

Description

This update to field manual includes documentation update on how to leverage the executor hooks dictionary.
Caldera pull request apache/caldera#3101

Type of change

• [x ] This change requires a documentation update

How Has This Been Tested?

Previewed mark down in editor. No issues.

Checklist:

• [ x] My code follows the style guidelines of this project
• [x ] I have performed a self-review of my own code
• [ x] I have made corresponding changes to the documentation
• [ x] I have added tests that prove my fix is effective or that my feature works

[Copilot]

Pull Request Overview

This PR adds comprehensive documentation for Caldera's plugin hooks feature, which allows plugins to intercept and modify abilities during runtime. The documentation explains how to leverage the executor hooks dictionary to customize ability execution behavior.

• Added detailed explanation of the executor hooks mechanism
• Provided step-by-step implementation examples with code snippets
• Demonstrated different criteria for targeting specific abilities or executors

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Corrected spelling of 'facilated' to 'facilitated'.

Suggested change

	Caldera provides plugins the ability to hook into the runtime when a link is added to any operation. This is facilated through a dictionary object in each executor ```executor.HOOKS```. The values in this dictionary contain function pointers to be called before the server queues the ability for execution.
	Caldera provides plugins the ability to hook into the runtime when a link is added to any operation. This is facilitated through a dictionary object in each executor ```executor.HOOKS```. The values in this dictionary contain function pointers to be called before the server queues the ability for execution.

[Copilot]

Remove unnecessary apostrophe - should be 'executors' not 'executor's'.

Suggested change

	2. Update your plugin service script (e.g., myplugin_svc.py) to parse ability files and their executors. Add logic to hook into the executor's you are interested in modifying.
	2. Update your plugin service script (e.g., myplugin_svc.py) to parse ability files and their executors. Add logic to hook into the executors you are interested in modifying.

[Copilot]

The YAML example shows 'hook: myspecialhook' as a top-level field, but the code example checks 'ability.additional_info['hook']'. The YAML should be nested under 'additional_info' to match the code implementation.

Suggested change

	hook: myspecialhook
	additional_info:
	hook: myspecialhook

[deacon-mp]

Can you address the above and resubmit for Review