Add OpenCRE as a map analysis resource

[Bornunique911]

Related Issue

This branch addresses:

• #469 Add OpenCRE itself to mapanalysis
• Add OpenCRE itself to mapanalysis #469

Problem

OpenCRE already acts as the central requirement graph, but it is not currently exposed as a selectable resource in map_analysis.

That means users can compare external standards to each other, but they cannot directly compare a standard against OpenCRE itself. This limits a useful workflow described in the issue, such as understanding how a standard maps into OpenCRE coverage.

Solution

This branch adds OpenCRE itself as a supported map-analysis resource.

1. Add OpenCRE to the standards list

The /rest/v1/standards response now includes OpenCRE so it can be selected like other map-analysis resources.

2. Add direct map-analysis support for OpenCRE

When one side of /rest/v1/map_analysis is OpenCRE, the backend now builds the result directly from CRE-to-standard links instead of sending the request through the normal queued standard-to-standard flow.

This works by:

• treating OpenCRE as the set of CRE documents in the local database
• matching the other selected standard through its linked CREs
• building a direct overlap result from those shared CRE relationships

3. Keep the implementation narrow

This branch only adds the minimal backend behavior needed for OpenCRE to behave as a map-analysis resource. It does not change the general gap-analysis queue model for other standard-to-standard requests.

Testing

Executed focused validation with:

./venv/bin/python -m pytest application/tests/web_main_test.py -k 'standards_from_db or supports_opencre_as_standard' -q