Add documentation endpoint for information about operations to create MCP possiblities

[GhostDog98]

This PR adds a new endpoint, /docs.
The description for this endpoint is: "Given the name of an operation, returns a json-formatted string containing the operation's documentation. The endpoint does not return documentation for any operations that may be called by the specified operation (for example, operations called by a "Magic" operation)."
An example request may look like:

curl -X 'POST' \
  'http://localhost:3000/docs' \
  -H 'accept: text/plain' \
  -H 'Content-Type: application/json' \
  -d '{
  "operation": "md5"
}'

And a sample response:

[
  {
    "module": "Crypto",
    "description": "MD5 (Message-Digest 5) is a widely used hash function. It has been used in a variety of security applications and is also commonly used to check the integrity of files.<br><br>However, MD5 is not collision resistant and it isn't suitable for applications like SSL/TLS certificates or digital signatures that rely on this property.",
    "infoURL": "https://wikipedia.org/wiki/MD5",
    "inputType": "ArrayBuffer",
    "outputType": "string",
    "flowControl": false,
    "manualBake": false,
    "args": [],
    "name": "MD5"
  }
]

My motivation for this PR is that this would allow an LLM to use cyberchef as a managed context protocol provider very easily, which would greatly improve its abilities.

[CLAassistant]

All committers have signed the CLA.

[GhostDog98]

Apologies for the delay and force push rebase, I had to change the username i signed my commits with.

[GhostDog98]

I'll be closing this for the time being due to #79 as that is far more pressing. Will reopen one that gets merged.