Creating a relevancy testing system for architecture gaps

[jlarson4]

Description

Designed a system that scores architectures based on downloads, model counts, and complexity to order which architectures should be prioritized in architecture-gaps.json

Type of change

• New feature (non-breaking change which adds functionality)

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have not rewritten tests relating to key interfaces which would affect backward compatibility