E2E: Track fabrication time in e2e tests

What does this MR do and why?

Describe in detail what your merge request does and why.

Track how long it takes for tests to fabricate resources.

Several things to note:

• Due to our metrics tracking separate specs, first implementation will not include fabrication in before(:all) blocks, since we don't have a data point to attach it to. Most likely v2 would have to implement separate runtime tracking for the whole _spec.rb file rather than single test.
• Fabrications can be nested so we can't just sum the time of each fabrication as top level fabrication time will always include the nested fabrication time. This is why we can only record time of top level fabrication. This can lead to somewhat incorrect result of api vs ui fabrication distribution if for example inside api fabrication a ui fabrication happens (most often PAT creation) which will bloat time of api fabrication.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.

Part of: https://gitlab.com/gitlab-org/quality/team-tasks/-/issues/1031