Add OpenCRE as a map analysis resource

[Bornunique911]

Summary

Closes #469.

Issue #469 asks to add OpenCRE itself as an option in Map Analysis so users can get views such as OpenCRE <-> SAMM.

This PR implements that by adding OpenCRE as a selectable map-analysis resource and handling OpenCRE comparisons through a dedicated direct-link backend path.

What this PR adds

When one of the selected standards is OpenCRE, the backend now:

• includes OpenCRE in /rest/v1/standards
• resolves the comparison through OpenCRE’s direct mappings
• returns results in the existing map-analysis response structure
• preserves the selected left side as the grouping side

This makes views such as:

• OpenCRE -> SAMM
• SAMM -> OpenCRE
• CWE -> OpenCRE

available directly from Map Analysis.

Implementation choice

For OpenCRE comparisons, this PR uses only direct Linked To relationships from OpenCRE CREs to the selected standard nodes.

That means:

• direct mappings are included
• indirect / automatic mappings are excluded

This keeps the OpenCRE view focused on explicit mappings rather than broader inferred overlap.

Resulting behavior

Standard <-> OpenCRE now behaves like a direct mapping view:

• Standard -> OpenCRE groups by the selected standard entries and shows their directly linked CREs
• OpenCRE -> Standard groups by CREs and shows their directly linked standard entries

For example, a case like CWE-1004 returns the directly linked OpenCRE mapping rather than a broader automatically related set.

Hover compatibility

The current Map Analysis popup infers direction from the one-step path payload.

To keep this PR backend-only, the direct OpenCRE fast path includes a small compatibility adjustment in the returned one-step path shape so the existing hover renders correctly for Standard -> OpenCRE without changing generic gap-analysis behavior.

This compatibility shaping is limited to the OpenCRE direct-link path only.

Validation

Focused regression:

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

[Bornunique911]

OpenCRE is now included as standards :

Comparison between ASVS and OpenCRE :

Comparison between CWE and OpenCRE :

Note: updated CWE and OpenCRE comparison screenshot after the fix

[robvanderveer]

It sort of looks okay, but I am afraid that CWE 1004 links to only one CRE, and not 8. So something's wrong.

[Bornunique911]

Hi @robvanderveer, thanks for calling out for the issue.

The issue was in the fetch logic where were also including the indirect links, now I have fixed it to only match direct links. So in the screenshot now we have only 1 mapping for CWE 1004 in CRE.

I also noticed an issue in hover logic, for now I have handled it at backend side.

[Pa04rth]

For me it looks Okay , will request @northdpole and @robvanderveer to review it too before merging.