Introduce String.replaceAll instance function

[darkdrag00nv2]

Work towards #2813

Description

Adds str.replaceAll(_ of: String, _ with: String): String function to Cadence.

---

• Targeted PR against master branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work
• Code follows the standards mentioned here
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[codecov]

Codecov Report

Attention: 4 lines in your changes are missing coverage. Please review.

Comparison is base (fa75807) 79.84% compared to head (57d4ad8) 79.84%.

Additional details and impacted files

@@                   Coverage Diff                   @@
##           feature/stable-cadence    #2814   +/-   ##
=======================================================
  Coverage                   79.84%   79.84%           
=======================================================
  Files                         343      343           
  Lines                       81056    81088   +32     
=======================================================
+ Hits                        64719    64747   +28     
- Misses                      14027    14029    +2     
- Partials                     2310     2312    +2     

Flag	Coverage Δ
unittests	79.84% <87.50%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files	Coverage Δ
runtime/sema/string_type.go	96.61% <100.00%> (+0.18%)	⬆️
runtime/interpreter/value.go	67.18% <84.61%> (+0.03%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[darkdrag00nv2]

Force push to resolve merge conflict.

[darkdrag00nv2]

@turbolent @dsainati1 Could you please take a look? Thanks!

[darkdrag00nv2]

@SupunS Should we merge this? Seems a relatively straightforward change.

[turbolent]

Sorry I missed this! The PR looks good, but the function needs to have its computation metered, as it performs a non-constant operation. The same also applies to the other stdlib PRs that got opened so far.

This might require "inlining" the replaceAll call to the Go stdlib, and calling ReportComputation with a new (?) common.ComputationKind

I opened #2879 to track this, see the details there.