1982318 - Make it possible to delete uploaded profiles from about:logging

Status: ASSIGNED

(Core :: XPCOM, enhancement, P2)

Description

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

Bug 1803607 added a way to upload profiles from about:logging. But currently there is no way to delete them if they are uploaded through about:logging.

We should:

1. Save the jwt token that we get from here (we save it in indexeddb in the frontend) That uploadResult is the jwt token that we just discard. We can include some more information from the profile data like we do in the profiler frontend.
2. Show a list of "uploaded profiles" in about:logging with a "delete" button on the side.
3. Send a request with that jwt token to the profiler server with the delete request (similar to here) when that button is pressed

Comment 1

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

Attachment: Bug 1982318 - Fix the prefs in about:logging tests r?padenot

They were fine in CI, but running them locally was showing some expected
failures about persisting some preferences.

Comment 2

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

Attachment: Bug 1982318 - Add profile storage logic and save the uploaded profiles in about:logging r?padenot

This patch doesn't use the code yet, it just adds the storage logic for
us to use in the following patch.

Comment 3

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

Attachment: Bug 1982318 - Add "uploaded profiles" section to about:logging with the ability to delete profiles r?padenot

Comment 4

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

Attachment: Bug 1982318 - Add tests for "uploaded profiles" section and profile deletion in about:logging r?padenot

Comment 5

[Nazım Can Altınova [:canova][:canaltinova on phabricator]]

Attachment: Bug 1982318 - Fix some flakiness in the about:logging tests r?julienw!

Previously, when we were saving the profile to disk, we getting the
profile path from the localized string. But it appears that due to some
rendering timing issues, the rendered text might not contain the path
yet. But we will always have it inside the data-l10n-args attribute.
That's why it's better to check that directly.