Resolve location of imported values

[turbolent]

Description

Follow-up to #3619

If we are translating imports of programs, e.g. import Crypto to the chain-specific address, we also must perform the same location translation when importing values.

This became evident while working on onflow/flow-go#6571, and specifically while updating the Emulator, which has a test case fro importing Crypto.KeyList. I've added a generic test case here, and will add a test case for Crypto.KeyList to flow-go in onflow/flow-go#6571.

---

• 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:master commit d96a90d
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