…est directly (#5180)

Since it was using the jest directly without setting the important
environment variables, `test-build-coverage` script was failing. If you
were to run `test-coverage`, because the first one was failing, it was
always stopping early without serving the files.

In the following commit, we are going to be using the sha1 code that we
have that relies on window.crypto. We have to add it to jest as well to
make sure that we don't break the tests.

…ata urls

Firefox bumped its version while working on this patch!

… selector (#5166)

This requires changes from [Bug
1921778](https://bugzilla.mozilla.org/show_bug.cgi?id=1921778) since it
adds the webchannel changes in the backend.

This PR adds the ability to retrieve the favicons for pages as a data
url, so we can display them easily in the frontend without needing to
fetch them from their url every time we open a profile.

This also changes how we use the `Icon` component and how we compute the
css class names for them. Let me know what you think!

Note that this doesn't change the other icons that we have in places
like call tree. I would prefer to do it as a followup as there are some
questions to answer there.

…ve favicons

…cons (#5182)

This PR adds default icons for extensions and pages. So if we don't have
any favicons for these, these default ones will be used in the tab
selector.

I'm not a fan of this solution, but I'm also not a fan of our current
way of handling this column. The icon itself is 14px but the parent
div's width is 10px. So I would prefer to change the parent's width
to 14px too, but this parent itself is not really responsible of
paddings arond this. It's the adjacent separator divs who are
responsible. So this other solution will be a lot more difficult.

…5187)

…5188)

Previously we were always including the profile `startTime` in the title
even when it was zero. It was resulting in a title that includes
`1/1/1970, 12:00:00 AM UTC`, which is not useful for anyone. This was
more visible in the Chrome profiles especially since they don't have a
metadata.

This patch changes this title algorithm to make sure that we don't print
the profile time when the profile `startTime` is zero. It also makes
sure that `(public)` annotation is properly added as well as all the
separators.

This changeset changes the type definition for marker schema
field types and for the marker schema itself, to include the new
field types 'flow-id' and 'terminating-flow-id'. It also has some
minimal changes to treat the new field types as if they were unique-string
fields.
Somewhat unrelated to flows, it also adds an optional `isStackBased`
field to the marker schema type, which is currently unused. This is
for #3141 .

Additionally, it increments the version of the two profile formats,
so that profiles with the new field types won't be loaded by
older front-ends.

This PR changes the type definition for marker schema field types and
for the marker schema itself, to include the new field types 'flow-id'
and 'terminating-flow-id'. It also has some minimal changes to treat the
new field types as if they were unique-string fields.
Somewhat unrelated to flows, it also adds an optional `isStackBased`
field to the marker schema type, which is currently unused. This is for
#3141 .

Additionally, it increments the version of the two profile formats, so
that profiles with the new field types won't be loaded by older
front-ends.

…ck color (#5201)

…elected in the tab selector (#5198)