Fix problem reports not being kept correctly

[Pururun]

Also restore secure view behaviour for Send report problem success screen.

---

This change is 

[linear]

DROID-508 Report a problem input not kept across navigation

The report a problem input isn't kept when navigating away from the report a problem view. Funnily enough, we even emphasize that we will keep the input in the case when we fail to send:

If you exit the form and try again later, the information you already entered will still be there.

The is a compose migration regression.

[sabercodic]

Reviewed 6 of 7 files at r1, all commit messages.
Reviewable status: 6 of 7 files reviewed, all discussions resolved

[albin-mullvad]

Reviewed 7 of 7 files at r1, all commit messages.
Reviewable status: complete! all files reviewed, all discussions resolved

[albin-mullvad]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Pururun)

a discussion (no related file):
Perhaps we should clear the input on logout? I'm not sure how it worked before 🤔

---

[albin-mullvad]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @Pururun)

a discussion (no related file):

Previously, albin-mullvad wrote…

Perhaps we should clear the input on logout? I'm not sure how it worked before 🤔

As mentioned offline, I suggest we keep the behavior we had before the regression was introduced.

---

[Pururun]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @albin-mullvad)

a discussion (no related file):

Previously, albin-mullvad wrote…

As mentioned offline, I suggest we keep the behavior we had before the regression was introduced.

Test on current production and email and message was not deleted if the user logged out, so we have the same behaviour as before.

---

[sabercodic]

Reviewable status: all files reviewed, 1 unresolved discussion (waiting on @albin-mullvad)

[albin-mullvad]

Reviewable status: complete! all files reviewed, all discussions resolved