* initial commit of new fragment for symptom screen

* Added relevant strings for symptom screen. Started editing xml of initial symptom screen

* Addded 3 selection options within symptom screen

* button id name change to something more relevant

* ID changes to be something more relevant to symptom scenerio.

* Implemented symptom initial screen logic. Temporary nav for testing.

* CircleCI formatting

* Adapted interoperability test provided by apopov

* Added accessibilty announcement on resume, fixed navigation for main page

* circleCI indentation fix

* removed ar & ru and updated default strings

* Adaption to ViewModel logic. Not yet complete

Adaption to ViewModel logic, attempting to align with implementation done with some interoporibility tasks: reusable layout files, etc.

* More ViewModel transformation additions

* revert nav from test. Circle CI formatting changes

* Update SubmissionSymptomIntroductionFragment.kt

* Removed old fragment based test

* Will implement navigation during marry session.

* Update SubmissionViewModel.kt

* Calendar button selection screen + required strings

* Custom calendar view

* Accessibility improved

* introduced data types for symptoms

* represent date by long in millis

* new TransmissionRiskVector

* Constants and formatting

* Naming changes requested

* Better event naming

* Update fragment_submission_symptom_intro.xml

* Finishing calendar implementation - still need to implement calendar widget

Surrounding calendar submission UI - minus calednar widget
Necessary strings

* Merged introduction and calendar screen.

Created calendar fragment screen,
Finished calendar XML view
Added required entries for choices in SubmissionViewModel
Adjusted Formatters for button selection.
Changed nav graph.

* + todo

* CircleCI code style changes

* EXPERT STUFF

* Latest push for marry session

* replaced transaction risk vector

* update textcolor on symptom indication change

* update buttons by code

* code formatting

* Added logic for Negative and No Information buttons and adjusted xml view to be more aligned with design

Added logic for Negative and No Information buttons and adjusted xml view to be more aligned with design

* disable next button when state is null.

* + readability

* Calendar screen logic adapted for button selection

* extracted domain logic from prototype and from transaction

* - not used events

* joint improvements

* removed unused events

* Calendar unsetSelection added

* detekt rules changed and formatting

* - calendar view refactor: CalendarCalculator singleton introduced for batter testing capacity
- unit tests added

* detekt issues

* Colors and styles cleared

* fixed strings

* maintained unit tests

* adopted changes from main nav graph to device for testers nav graph

* reverted comment

* made start of symptoms nullable

* tests

* Adjusted navigation, fixed dark theme

* Update Project.xml

* use of postValue() in SubmissionViewModel.kt

* Added direction in tester nav graph

* improvements required by review

* moving companion

* moving companion

* moving companion

* fixed issues from partner review

* fixed issues from partner review

* fixed issues from partner review

* fixed issues from partner review

* fixed issues from partner review

* using utc

* edge case tests

* made inner class

* Refactored Symptoms Class Name (+data class)

* Change SubmissionViewModel scope to ensure that the same viewmodel is used to store submission data.

* extracted null check + log

Co-authored-by: Luka Harambasic <luka.harambasic@sap.com>
Co-authored-by: chris-cwa <chris.cwa.sap@gmail.com>
Co-authored-by: Alexander Alferov <a.alferov@sap.com>
Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>
Co-authored-by: Matthias Urhahn <darken@darken.eu>
Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>

* Removed blanked internet connection UI state. New Dev base for pipeline issues

Removed the blanket internet connection status:

Removed the connection state from TracingStatusHelper
Adjusted formatters which use the adjusted TracingStatusHelper
Removed connection logic from various fragments (SettingsTracingFragment, etc.)
Adjusted XML views (Settings Fragment: no connection card, etc.)
Adjusted automated tests that previously included the connection state.
Closes JIRA task EXPOSUREAPP-1572

* Update FormatterSettingsHelperTest.kt

* Update fragment_main.xml

deviceForTesters was still using connection state.

* Update Project.xml

* Update FormatterSettingsHelperTest.kt

Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>

* Disable klint debug output to make it easier to find the actual error in the log.

* Setup jUnit5 & kotest.

* Add base classes for testing to setup log output.

* Introduce class `DeviceStorage` to check (or request on newer APIs) free space.

Rel. EXPOSUREAPP-2259

* Add test cases for failure modes.

* Make it obvious that the check should not be executed on the ui thread.

* Try fall back to legacy method if the API26+ version fails.
If that also fails, throw the exception and let the caller handle it.

* Wire up injection annotations.

* Remove unused mockito testing dependency.

* klint...

Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>
Co-authored-by: Jakob Möller <jakob.moeller@sap.com>

* Ship a common codeStyle that matches KLint.

* The config for newlines at end of files should also have a new line at it's end :D.

Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>
Co-authored-by: Jakob Möller <jakob.moeller@sap.com>