[Compiler] Refactor vm.Value and related operations to be independent of the vm.Config

[SupunS]

Work towards #3693

Description

Similar to the refactor in the interpreter, avoid the vm.Config from being passed into value related functions (StaticType, Transfer, etc.) at the VM side. Instead, pass only what is needed for each function, as an interface (re-use interpreter's interfaces wherever possible).

In the follow-up PR #3819, similar interfaces are defined at the interpreter (e.g: ValueTransferContext) and decoupled more of interpreter.Values.

The idea is to gradually decouple values of both sides (both vm and interpreter), and make bring the interfaces defined in both sides to an exact match, which will allow us to switch and replace vm-values from the interpreter-values.

---

• 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

[github-actions]

Cadence Benchstat comparison

This branch with compared with the base branch onflow:feature/compiler commit e6f27ac
The command for i in {1..N}; do go test ./... -run=XXX -bench=. -benchmem -shuffle=on; done was used.
Bench tests were run a total of 7 times on each branch.

Collapsed results for better readability

[turbolent]

Great idea and great work! 👏