New texts for the dialog requesting consent for key submission/warning others(EXPOSUREAPP-3979) #1790

* All your strings are belong to us!

* Submission your consent screen

* Unit test fix

* Unit test fix

* Unit test fix

* Refactor view model, tests and events

* Fixed test

* Lint fix, added id to bottom divider

* Your test result available screen

* Formatting

* Lint fix

Merge 1.8.x into 1.9.x (DEV)

Submission Flow: Positive test result with given user consent (EXPOSUREAPP-3680)

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

* Small translation update (DEV)

* Update Corona-Warn-App/src/main/res/values-de/strings.xml

Co-authored-by: Sabine Loss <44154356+SabineLoss@users.noreply.github.com>

Co-authored-by: janetback <68653277+janetback@users.noreply.github.com>
Co-authored-by: Sabine Loss <44154356+SabineLoss@users.noreply.github.com>

* move legal strings
adjust grey area to hold legal text

* remove duplicates

# Conflicts:
#	Corona-Warn-App/src/deviceForTesters/java/de/rki/coronawarnapp/test/risklevel/ui/TestRiskLevelCalculationFragmentCWAViewModel.kt
#	Corona-Warn-App/src/main/java/de/rki/coronawarnapp/storage/RiskLevelRepository.kt
#	Corona-Warn-App/src/main/java/de/rki/coronawarnapp/worker/DiagnosisTestResultRetrievalPeriodicWorker.kt
#	Corona-Warn-App/src/main/res/values-bg/strings.xml
#	Corona-Warn-App/src/main/res/values-de/strings.xml
#	Corona-Warn-App/src/main/res/values-en/strings.xml
#	Corona-Warn-App/src/main/res/values-pl/strings.xml
#	Corona-Warn-App/src/main/res/values-ro/strings.xml
#	Corona-Warn-App/src/main/res/values-tr/strings.xml
#	Corona-Warn-App/src/main/res/values/strings.xml

* Remove "lastTimeDiagnosisKeysFromServerFetch" and replace it with less missleading data.
While it was called "lastTimeDiagnosisKeysFromServerFetch" it was actually "last time we submitted keys to google".

* To decide whether to refresh in "onResume", we now use "has there been any submission to the ENF?"
* To display a timestamp on the risk card, we take the last successful submission to the ENF as the risk card displays the calculation results based on the latest submission. While we could use the last calculated risk level result timestamp, we currently also trigger risk calculations if there are no new submissions to the ENF, which would mean the timestamp is updated even though the result is not based on new data.

I've also fixed the test fragment button behavior and added descriptions, the "Reset risk level" button surfaced the initial issue because it behaved like a "do a 75% data reset" button.

* Tests and LINTs

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

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

* Don't show last risk contact when tracing is disabled.

* Add unit test.

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>

Co-authored-by: Chilja Gossow <49635654+chiljamgossow@users.noreply.github.com>

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

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

* Fix displayed details in tracing inactive states.

* Simplified UI states.
Replaced RiskLevel and RiskLevelConstants with RiskState { LOW; HIGH, FAILED }.

* Fix low risk card missing the encounters if there have been more than 0.

* Fix missing card divider/border on error cards in light mode.

* Fix merge regression.

* LINTs

* Fix progress card colors on white card background color.

* Fix progress card colors on white card background color.

* Don't allow negative active tracing days.

* Revert sync behavior (extra PR)

* Address PR comments.

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

* Remove minimum tracing time requirement.

* LINT issues.

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

Change-Id: Ic383ee5f17031502ba2a5b1e0a5f5f2dec23cb48

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

* Consent custom view + formatting

* Proper strings.xml

* Switch to constraint layout

* Flatten view hierarchy.

Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>

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

Low Risk after update from 1.7.0 RC8 (in increased risk state) to 1.8.0 RC2 (EXPOSUREAPP-3988) (#1745)

* check whether there already is a v2 exposure

* check preconditions when selecting task for execution - not when scheduling it

* fixed tests

* fixed detekt

* removed todo that was already addressed by d4rken

* updated tests

* https://github.com/corona-warn-app/cwa-app-android/pull/1745#discussion_r532568615



Co-authored-by: harambasicluka <64483219+harambasicluka@users.noreply.github.com>
Co-authored-by: Matthias Urhahn <matthias.urhahn@sap.com>

* Add missing RiskLevelStorage reset call when using the internal app reset functionality.

* Improve TaskController logging.

* Use the day/hour of the last key package download to determine whether the key pkgs are outdated when calculating the risk level.

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

* Adding missing log tags, otherwise displays "BaseContinuationImpl" etc.

* Remember the last risk level result for which we did a change check.
This fixed the issue that if no new risk level calculation happened, and the last one triggered a notification,
killing and restarting the app would also trigger a notification.

Co-authored-by: Ralf Gehrer <ralfgehrer@users.noreply.github.com>
Co-authored-by: BMItter <46747780+BMItter@users.noreply.github.com>

Co-authored-by: BMItter <46747780+BMItter@users.noreply.github.com>