Fix default compute limit deprecation warning

[adbario]

Description

Fixes the warning about the deprecated default compute limit for transactions.

FCL/SDK Deprecation Notice
==========================
    
The built-in default compute limit (DEFAULT_COMPUTE_LIMIT=10) is
deprecated and will cease to work in future releases of FCL/SDK.

Previously, providing a compute limit for transactions was optional, and a fallback existed (DEFAULT_COMPUTE_LIMIT=10). Compute limits may still be applied explicitly in a transaction.

flow-js-testing already has a way to set the limit per transaction, but the default value is also required now.

The value is set to 999 as it was in interactions, and the value is now imported to interactions from the config file just to have it in one location.

Also, a configuration test is added.

More information about the deprecation https://github.com/onflow/fcl-js/blob/master/packages/sdk/TRANSITIONS.md#0009-deprecate-default-compute-limit

---

For contributor use:

• 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 – No relevant parts in documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels – No permissions to add labels

[changeset-bot]

🦋 Changeset detected

Latest commit: dd4ecba

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@onflow/flow-js-testing	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[justinbarry]

@adbario Can you add a changeset file to this PR and I can merge it down. Thank you very much!

[justinbarry]

Here are the instructions:

Thank you for your contribution! Would you be able to add a
changeset file for this? Just run npm run changeset at the root and follow the prompts using these conventions:

• MAJOR version when you make incompatible API changes,
• MINOR version when you add functionality in a backwards compatible manner, and
• PATCH version when you make backwards compatible bug fixes.

[adbario]

@adbario Can you add a changeset file to this PR and I can merge it down. Thank you very much!

Thanks @justinbarry 🚀

Changeset added, sorry I missed that before.