Move trace descriptions out of success/failure sentences in emails

[AntonKhorev]

Fixes #4012. As I say in #4012 (comment) the current success/failure sentences are too long because we try to put in trace name/description/tags into them. I don't think anyone wants to read sentences that long. Shorter sentences won't have to be combined from parts, which will improve translatability.

Before

HTML success email:

After

HTML success email:

HTML failure email:

Plaintext success email:

Hi fakeuser1,

It looks like your file loaded successfully with 295 out of a possible 295 points.

Your file details:

Filename
	11716462.gpx
URL
	http://openstreetmap.example.com/user/fakeuser1/traces/100
Description
	new trace description here
Tags
	new, trace, tags, here


All your successfully uploaded GPX traces can be found at http://openstreetmap.example.com/traces/mine

Plaintext failure email:

Hi fakeuser1,

It looks like your file failed to be imported as a GPS trace.

Your file details:

Filename
	Screenshot_from_2025_01_06_12_50_06.png
Description
	new trace description here
Tags
	new, trace, tags, here


Please verify that your file is a valid GPX file or an archive containing GPX file(s) in the supported format (.tar.gz, .tar.bz2, .tar, .zip, .gpx.gz, .gpx.bz2). Could there be a format or syntax issue with your file? Here is the importing error:

==
Fatal error: Start tag expected, '<' not found at :1.
==

More information about GPX import failures and how to avoid them can be found at https://wiki.openstreetmap.org/wiki/GPX_Import_Failures

[nenad-vujicic]

This works and looks great on my side. Thank you very much!

I would just suggest putting the property and value in the same row, as shown in

However, this is a bit subjective and can be addressed in another PR if others prefer.

[AntonKhorev]

I would just suggest putting the property and value in the same row

In the plaintext version? I didn't do that because I didn't want to count characters in localization strings.

[tomhughes]

I don't think we need to worry too much about the details of the text version as most people are never going to see it.

This looks pretty good to me I think, thanks.