Add tests for enum usage as transaction parameters

Add test for circular resources

Always return parser errors gracefully

…ort-251

…ort-250

Allow validation of `Account.capabilities.get/borrow/publish`

Fix runtime type of Account_Inbox_claim() function

Currently, some migration tests reuse storage for migration.
It can lead to tests failing when the storage cache gets
out of sync with underlying storage.

For example:
1. Use storage 1 to store valueA in public domain directly.
2. Use storage 2 to store valueB in public domain via
   ExecuteTransaction().
3. Reuse storage 1 for migration.  Here, migration
   only sees valueA from cache instead of both values.

This commit prevents out-of-sync issues by creating new
runtime.Storage for migrations instead of reusing old storage.

follow-up from onflow/cadence-internal#249
perform return value conversion/boxing for all invocations, like internal invocations,
not just invocation expressions

…tionValue.invoke

ensure parameter is properly converted/boxed

…tionValue.invoke

…nValue.invoke

…d of FunctionValue.invoke

… instead of FunctionValue.invoke

… FunctionValue.invoke

… FunctionValue.invoke

… of FunctionValue.invoke

This commit removes unreferenced slabs when updating dictionary
with enum keys to prevent them from remaining in storage.

Background

Currently, unreferenced slabs can be created by updating dictionary
if the key is enum type and key already exists.

More specifically,
- Cadence creates and stores enum key (in its own slab) in storage
  during Transfer() to update underlying atree map element.

- If same key already exists, atree map only updates map value without
  referencing the newly created enum key.

- Newly created enum key is not referenced (aka dangling, unreachable)
  in the underlying atree map.

This issue only affects enum key type because enum type is the
only type that:
- can be used as dictionary key (hashable) and
- is transferred to its own slab.

Large string key isn't affected by this issue because large string
isn't stored in its own slab during Transfer().

Currently enum type is the only composite type that needs to be
removed explicitly when used as key to update existing dictionary
element.

However, (as noted by Supun) Cadence might in the future add
support for other composite types as key.

This commit removes enum type checking to support new composite
key types to be added to Cadence language in the future.

Update version.go

Port bug fixes from internal repo

…ort-263

Prevent leaving unreferenced slabs in storage while updating dictionary with enum key

…ort-263

Fix invocation boxing

…/sync-v1.0-master

Merge v1.0 into master

… better, dedicated error

Co-authored-by: Supun Setunga <[email protected]>

Improve `result` variable

…ructing and decoding type ID

Explain the reason for support parsing legacy restricted types

Remove legacy content

…/restructure

Move  subdirectories under `runtime` to top level

…/restructure-2

Move tests under `runtime` to `tests` directory

…re/string-templates