Provide proper ISO 8601 timestamps in crash report emails

[TheAssassin]

Checklist

• I made sure that there are no existing issues - open or closed - which I could contribute my information to.
• I have read the FAQ and my problem isn't listed.
• I'm aware that this is a request for NewPipe itself and that requests for adding a new service need to be made at NewPipeExtractor.
• I have taken the time to fill in all the required details. I understand that the feature request will be dismissed otherwise.
• This issue contains only one feature request.
• I have read and understood the contribution guidelines.

Feature description

The crash report emails contain incomplete timestamps in an arbitrary format à la YYYY-mm-dd HH:MM. They should be sent in the ISO 8601 format.

Edit: We could directly normalize the time to UTC, too, but if it is sent in the ISO 8601 format, the timezone is encoded properly anyway and can be parsed.

Why do you want this feature?

While we don't need seconds precision, we need timestamp information. Glitchtip/Sentry/... reject timestamps that are in the future. Right now, the importer just discards such emails. Alternatively, we would have to replace the timestamp in the email with the current local time during the import, further reducing the accuracy.

Additional information

https://github.com/TeamNewPipe/CrashReportImporter/

CC @TobiGr

[Nikunj-Aggarwal]

Could you please assign me this issue?