Ignore empty partials coming from dynamic sources

[krzksz]

What issue does this pull request address?

So I finally managed to reproduce a recent situation where I'm getting the The page cannot be profiled error.
During the investigation, I noticed the following error in extension's devtools:

The issue occurs when a certain page uses a dynamic source in one of the rich text areas. Here I set up an example product page on my test store (password: pierogi), which references the product's vendor.

It triggers the error, because its entry contains only a code snippet:

so the const nameParts = entry.partial.split('/'); part fails.

What is the solution

I don't think showing a dynamic source entry on the flamechart would be actionable. Also, the parent that renders it still included properly.

That's why I decided to skip any entries that don't have the .partial defined, which fixes the issue.

What should the reviewer focus on and are there any special considerations?

Fixes #121, fixes #137, fixes #138, fixes #139, fixes #140.

[mgmanzella]

tophatting looks great thank you!