Restructuring repository based on feedback

[jhbeskow]

🎟️ Tracking

🚧 Type of change

• 🧹 Tech debt (refactoring, code cleanup, dependency upgrades, etc.)

📔 Objective

Restructuring repository based on feedback from Matt Bishop.

📋 Code changes

• Multiple: All changes are based on refactoring request

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[withinfocus]

Didn't review exhaustively (such as README contents) but this seems solid. Once it merges and we prepare for release we can do a thorough review of current repository contents.

Optional and can be done later: changing the Renovate config file match here too.

[Thomas-Avery]

Structure changes LGTM, one small thing

[tangowithfoxtrot]

Tested local CLI workflow, VS Code debugger, and tests ✅

Thanks for doing this so quickly!