Job output transform

[OlivGruwe]

• Add support for various GeoTIFF formats, allowing flexible handling and representation of GeoTIFFs in outputs
  (fixes #100 <https://github.com/crim-ca/weaver/issues/100>_).
• Add support for GET /results/{id} and GET /outputs/{id} routes to enable direct access to individual
  job result items by ID. This enhancement includes: support alternate representations based on the Accept header.
  If an alternate format (e.g., YAML for a JSON source) is requested it will be automatically generated and returned.
  Link headers containing all possible output formats, allowing retrieval via query parameters
  (e.g., output?f=application/x-yaml). (fixes #18 <https://github.com/crim-ca/weaver/issues/18>_).

[fmigneault]

There's a few linting issues that can be resolved automatically using the make fix[...] targets.
Validate as well using make check[...] targets any other flagged issues that might need some manual adjustments. I didn't comment on all of them.

I did not go in depth into the actual implementation of the transform functions.
I think there is a few tests missing to validate that the actual results from each transformation is valid (eg: pixel values from one format to another are properly rendered or expected text from one format to another is properly structured).

[fmigneault]

This change is not valid. Removing format applies only for ogc+strict, not old+strict since "old" requires the format key.

[Nazim-crim]

let me know if this change is correct

[fmigneault]

Add indication of the rel used for those links.

Provide one change entry about the added weaver.transforms module and a brief explanation (eg: like the other comment about the test docstring) indicating the dynamically added transform formats.

Remove the "No change" entry.

[fmigneault]

@Nazim-crim
There's a few "FIXME https://github.com/crim-ca/weaver/issues/18" under https://github.com/crim-ca/weaver/blob/master/weaver/wps_restapi/api.py
In most cases, it should just be a matter of uncommenting them, but we need to check if all cases of #18 are handled (eg: calling an output that wasn't requested initially must return the http://www.opengis.net/def/exceptions/ogcapi-processes-1/1.0/no-such-output error).

Details of the requirement: https://docs.ogc.org/DRAFTS/18-062r3.html#req_core_job-results-exception-no-such-output

[Nazim-crim]

@fmigneault This should cover the different comment and fix #18 output error code. Let me know if there's other fix to applu