Make geh-aggregations production grade

[BjarkeMeier]

Synopsis

As a team member I want the repo state to be production grade So that the repo meets the "production grade" expectations of the architects and business

Scope

This story is production grade except for documentation, which is addressed in #775.

Acceptance-Criteria

• [x] AC1: All non-production grade content of the repo has been either removed or clearly marked as such (for example by moving to "poc" og "archive" folders)
• [x] AC2: All code has suitable (unit/integration/domain) test coverage.
• [x] AC3: Code coverage metrics doesn't include non-production code and meet the expectations (which are what?)
• [x] AC4: The developers have confidence that the code is deployed as working software
• [x] AC5: Existing deployed code must conform to the team standard with working software

Tech-Notes

Tasks

• [ ]

[BjarkeMeier]

Notes for tester: I went through most of the repo settings that we can setup ourselves. I've requested configuration of the repo from team MightyDucks. README.md and other (open-source) documentation will be added in #775. I've added required repo files.

[laskli]

Repo documentation read through and nothing seems to be missing.