MAPEX-178: fix veris bugs

[emeth1]

What changed

• veris counts on all mappings match
• all techniques from all domains build correctly
• capability groups and capabilities with no mappings not in capability groups / capabilities list
• capabilities with no mappings not added to total mappings count
• non_mappable capability pages built only if the project has non_mappable comments

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 45 lines in your changes are missing coverage. Please review.

Project coverage is 22.76%. Comparing base (39524b7) to head (156be25).

Files	Patch %	Lines
src/mappings_explorer/site_builder.py	0.00%	45 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #83      +/-   ##
==========================================
- Coverage   23.11%   22.76%   -0.36%     
==========================================
  Files          11       11              
  Lines        1484     1507      +23     
==========================================
  Hits          343      343              
- Misses       1141     1164      +23     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[github-actions]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-178_fix_veris_mismatch_counts/

[mehaase]

I'm still not seeing a perfect match on all counts. For example, value_chain.development says 26 mappings in the capability groups table, but if I search in the All Mappings table, I only get 23 results.

I clicked through to the "value_chain.development" page and compared the results, and I noticed the 3 results at the end have a capital V: Value_chain.development, and I guess this is why they are counted differently? We may want to consider finding and fixing these VERIS mappings that have upper case letters in unexpected places.

Here's another example from GCP: cloud_logging should have 1 mapping but shows up as zero in the All Mappings table. On the capability group page I see that 1 mapping but don't see any ATT&CK technique (can't scroll horizontally).

If we need to create separate issues for these, let me know.

[tiffb]

I'm not seeing links in the GCP and AWS non-mappings tables, and therefore I can't find non_mappable capability pages built for these projects which have non_mappable comments.

[github-actions]

This PR has been published to https://mappingsexplorer.z13.web.core.windows.net/MAPEX-178_fix_veris_mismatch_counts/

[emeth1]

I'm not seeing links in the GCP and AWS non-mappings tables, and therefore I can't find non_mappable capability pages built for these projects which have non_mappable comments.

I don't think it rebuild yet when you checked.
Can you check again now and confirm whether or not you see the correct non mappable table? Thanks.

[tiffb]

I'm not seeing links in the GCP and AWS non-mappings tables, and therefore I can't find non_mappable capability pages built for these projects which have non_mappable comments.

I don't think it rebuild yet when you checked. Can you check again now and confirm whether or not you see the correct non mappable table? Thanks.

I'm seeing the correct tables & pages - looks good! thank you