feat!: read/write context/permission

[da1suk8]

Description

This PR is related to #263.

#[callable_points] macro (NOT #[callable_point]) was created to expose read-write permissions to WASM using the _get_callable_points_properties().

This macro is used as follows.

#[callable_points]
mod callable_points {
    use super::*; 

    #[callable_point]
    fn foo(_deps: DepsMut, _env: Env, ...) {} // exposed to WASM
    
    #[callable_point]
    fn bar(_deps: Deps, _env: Env, ...) {} // exposed to WASM

    fn foobar() {} // NOT exposed to WASM
}

#[callable_point] is used as a mark rather than an attribute macro.
Only those with #[callable_point] above the function will be exposed to WASM.
It is also used for functions that manage read-write permissions for each function.

In the above example, the _get_callable_points_properties() can be used to retrieve the following map.
(true is read-only, false is read-write)

{
    "foo": CalleeProperty { is_read_only: false }, 
    "bar": CalleeProperty { is_read_only: true }, 
}

I also added a contract called intermediate-number, which has the roles of callee and caller.
Only sub is intentionally made a function with read-write permission.

The code expanded in macro can be viewed below.

$pwd
./contracts/number
$cargo expand --target wasm32-unknown-unknown

First, it may be necessary to add cargo expand and the target of wasm32-unknown-unknown.

• https://crates.io/crates/cargo-expand

Closes #263

Types of changes

• Bug fix (changes which fixes an issue)
• New feature (changes which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• ETC (build, ci, docs, perf, refactor, style, test)

Checklist

• I followed the contributing guidelines.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• The PR title and commits are followed conventional commit form.

[loloicci]

Write what the callable_points macro does in the docs.
"Function attributed with this macro must take deps..." is not suitable for this macro.

5d38732#diff-484ed4ec90b9bea6e333d2819a67f7b7421528d49e411d19fb93f25105e070abR96

[loloicci]

In this code, serialization of the map (name -> permission) is done in generated code. But, we can serialize it in macro (compile time) and use serialized binary in generated code.

[Kynea0b]

There is a typo in the command in Description. Please add n at the end.
wrong: $cargo expand --target wasm32-unknown-unknow
right:$cargo expand --target wasm32-unknown-unknown
@da1suk8

[Kynea0b]

LGTM

[da1suk8]

Finschia/wasmvm#93 (comment)

The read-write permission was confusing, so the structure has been modified.
The structure is as follows. (Ex: contract of number)

{
    "sub": CalleeInfo { is_read_only: false }, 
    "add": CalleeInfo { is_read_only: false }, 
    "number": CalleeInfo { is_read_only: true }, 
    "mul": CalleeInfo { is_read_only: false }
}

[loloicci]

Sorry for canceling approval, but recheck these comments.

#270 (comment)
#270 (comment)
I missed c337ae7, sorry.
Never mind.

[Kynea0b]

LGTM