[META] Create a reusable "Prompt Entity" and field

Problem/Motivation

Prompting is a complicated iterative process. Most modules use a text field to store the prompt but this is far from an ideal experience if a user is regularly engaging in prompting that is mission critical.

Proposed resolution

• Create a new "Prompt" entity
• Make it so modules and entities can add a prompt field that uses prompt entities in it, instead of just pure text
• The individual prompt entities can have meta data such as a title, tags and notes (for example whats the purpose of the prompt.
• The prompt can have revisions turned on for it even if the overall entity doesn't. This is especially important as prompting is a iterative process and the prompts can become large and mission critical
• If they are config entities they could be stored in code and backed up in git
• We can provide a CK editor like experience for prompt engineering including some basic synatx highlighting (Seperating context, from data, from examples if using delimiters, seperating code from the actual prompt for example). Or tools such as using @ to pull in tokens that are relevant.
• There can be a prompt library to search and find prompts you have permissions to edit and see where they are used.
• Prompts can be cloned or reused across multiple places.

Remaining tasks

User interface changes

API changes

Data model changes