OCL Mapper to use the new generic prompt invoke endpoint

[paynejd]

OCL Mapper currently uses the /match/recommend endpoint. This is hard-coded and tied to a single prompt. We want it to use the new general purpose endpoint, and we want invoke to follow the OCL/FHIR convention of prepending a dollar sign for operations instead of resources. So it should now be this:

/prompts/:key/$invoke/

Input variable processing is currently hard-coded in the old /match/recommend/ endpoint workflow. This must be moved over to the new model and triggered based on an attribute of the prompt: prompt_template.processing_method. Allowed values:

• None
• "candidates-core-attributes-only" -- or something like this

Note that we will have lots of processing pipelines in the future.

Acceptance Criteria

• Generic prompt invoking endpoint looks like this: /prompts/:key/$invoke/
• Input variable processing part of the new /prompts/:key/$invoke/ pipeline
• Mapper uses the new generic endpoint
• After testing, the old endpoint is retired

[snyaggarwal]

@paynejd $invoke needs to use Openrouter._to_bridge and Openrouter._to_scispacy methods to strip down the content that goes into prompt (#2309)

We can rename these methods generically

[snyaggarwal]

@paynejd I have updated and merged everything to _to_essential(candidate) method and it handles scispacy/bridge/semantic. This needs to be used inside invoke

[paynejd]

If prompt_template.action_type = match-recommend then apply the _to_essentials function before passing over to execute_prompt

[snyaggarwal]

@paynejd this is deployed