Meter computation in new stdlib functions

[turbolent]

Issue to be solved

Some of the new stdlib functions perform non-constant operations, which require computation metering:

• Master
  • Introduce String.join function #2762
  • Introduce map in Fixed/Variable sized Array types #2737
  • Introduce filter in Fixed/Variable sized Array types #2678
  • Introduce reverse in Fixed/Variable sized Array type #2654
• Master, not merged yet
  • Introduce reverseInPlace in Variable/Fixed size Array #2626
• Stable Cadence
  • Introduce String.replaceAll instance function #2814
  • Introduce String.split function #2791

Suggested Solution

Implementations should call ReportComputation, potentially with a new (?) common.ComputationKind.

Metering might also require "inlining" existing calls to the Go stdlib, so that each iteration of an operation can be metered up-front.

[turbolent]

@SupunS can you please have a look at this with @darkdrag00nv2 this/next week? The PRs that got merged into master have a high priority, as they need to get metered before the spork, the ones for Stable Cadence have a lower priority