Include the Monarch link app as a service on IMAGE-server

[VenissaCarolQuadros]

This PR merges a containerized version of the Monarch web application that links the IMAGE-TactileAuthoring tool to the Monarch client.

As per discussions, this application has been made into a service on the IMAGE-server. New channels can be created and existing channels can be updated by the authoring tool by posting to https://monarch.unicorn.cim.mcgill.ca/create/. The JSON can be accessed by the Monarch client by getting from https://monarch.unicorn.cim.mcgill.ca/display/. Resolves #888.

Testing:

• Checked that restarting container clears previously created channel
• Checked that a new channel can be created using publish on the authoring tool and getting the same on the Monarch

  <svg width="254.00000000000003" height="105.83333" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" version="1.1" xml:space="preserve">
  <g class="layer" data-image-layer="Layer 1">
  <ellipse cx="59.5" cy="27.82" fill="#FF0000" id="svg_1" rx="27" ry="25" stroke="#000000" stroke-width="5"/>
  </g>
  </svg>

  was published on code 123456.

• Checked that a channel can be updated when the code and secret id is correct Graphic on 123456 was updated to

  <svg width="254.00000000000003" height="105.83333" xmlns="http://www.w3.org/2000/svg" xmlns:svg="http://www.w3.org/2000/svg" version="1.1" xml:space="preserve">
  <g class="layer" data-image-layer="Layer 1">
  <rect fill="#FF0000" height="34.62" id="svg_2" stroke="#000000" stroke-width="5" width="84.83" x="26.47" y="33.31"/>
  </g>
  </svg>

  and the change was observed on the Monarch

• Checked that update fails when the secret id is incorrect The update failed when the secret key was changed

Required Information

• [x] I referenced the issue addressed in this PR.
• [x] I described the changes made and how these address the issue.
• [x] I described how I tested these changes.

Coding/Commit Requirements

• [x] I followed applicable coding standards where appropriate (e.g., PEP8)
• [x] I have not committed any models or other large files.

New Component Checklist (mandatory for new microservices)

• [x] I added an entry to docker-compose.yml and build.yml.
• [x] I created A CI workflow under .github/workflows.
• [x] I have created a README.md file that describes what the component does and what it depends on (other microservices, ML models, etc.).

OR

• [ ] I have not added a new component in this PR.

[VenissaCarolQuadros]

I ran additional tests with POST requests with incorrect/ omitted fields. It now returns 400 in these cases.

[VenissaCarolQuadros]

Made the requested changes. I also noticed that I was not saving 'title' to JSON- I've included it and also made it possible to change this when 'update/' is called.

Also, an exception was being raised when 'display/' was called on a valid ID that didn't exist in the JSON since abort() raises an exception.