Remove lists profiling

[fortmarek]

Fixes #89

What

Remove lists profiling code in favor of using @shopify/react-native-performance-lists-profiler library.

🎩

Check out the examples, see whether the events are still reported in the console (do not check the plugin, that will not work until a new release with this PR is released).

[caution-tape-bot]

👋 It looks like you're updating JavaScript packages that are known
to cause problems when duplicated.

You can deduplicate them with the yarn-deduplicate utility:

npx yarn-deduplicate --packages graphql react react-dom webpack
npx yarn-deduplicate --scopes @shopify @apollo

If running these commands doesn't produce a change in your yarn.lock file,
you didn't have duplications in these packages and can carry on.

A duplicate React version may cause an invalid hook call warning.

React context providers usually use module-scoped globals as their
default context values. Multiple versions of such packages will yield
multiple global instances, resulting in oblique runtime errors.

[ElviraBurchik]

I realised that if we ever open-source this library, it won't contain profiling utils - they all belong to react-native-performance now. Not a blocker, just thinking out loud whether the package should come with utils if react-native-performance is not open-sourced

[fortmarek]

Not a blocker, just thinking out loud whether the package should come with utils if react-native-performance is not open-sourced

That's a good point - before opensourcing this, we should look into how to make the profiling tools available to others. It also depends on how soon we will opensource this component compared to react-native-performance.