fix: read/write context/permission

[da1suk8]

Description

This PR is related to Finschia/cosmwasm#263, Finschia/cosmwasm#270

The read/write permissions of dynamic link caller functions were not properly inherited by callee environment, so fixed this.

There are a total of four possible combinations of caller and callee function read-write permissions.
The read-write permission is inherited by callee with the following rules.

If the caller's permission is read-only and the function of callee is read-write, an error occurs.
If the caller's permission is read-only and the function of callee is read-only, the callee's permission is set to read-only.
If the caller's permission is read-write and the function of callee is read-write, the callee's permission is set to read-write.
If the caller's permission is read-write and the function of callee is read-only, the callee's permission is set to read-only.

When you build a contract that has the role of callee for dynamic link in cosmwasm, the following function is exported in WASM.

  (export "_get_callable_points_properties" (func ..))

The return value of the function is a Map that takes the function name as a key and returns a read-write-permission.
True is read-only.
(This example is number contract)

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

The read-write permission is brought from this function and inherited by the instance of callee.

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 a test if it is able.
And, isn't it needed some verification in storing the code? If it has callable point export, the listing function export is also needed after it.

[da1suk8]

@loloicci

I am thinking of writing the test in lbm-sdk.
Also, verification in storing the code is considered to be done on the cosmwasm side.

[kokeshiM0chi]

@da1suk8
There are only 4 patterns of authority setting rules, so I want you to write them explicitly in the description.
For example:
If the caller's permission is readOnly and the callee's is readwrite, the calllee's is set to readOnly.

[kokeshiM0chi]

LGTM

[da1suk8]

CI is failing for the same reason as below.

#89 (comment)

CI fails with a race error and this error is caused even without this PR. A test added with this PR catch the race error of the cGetContractEnv. And we will solve this error in another PR.

[loloicci]

When you build a contract that has the role of callee for dynamic link in cosmwasm, the following function is exported in WASM.

(export "_list_callable_points" (func ..))
The return value of the function is a Map that takes the function name as a key and returns a read-write-permission.
True is read-only.
(This example is number contract)

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

_list_callable_point does not describe which (readonly or read-write) is true and which is false. How about changing _list_callable_point_is_readonly?

[da1suk8]

Finschia/cosmwasm#270 (comment)

Along with the modification of cosmwasm, I also modified here.

[da1suk8]

Added 1a56bcd because the name of the variable was not appropriate.

[loloicci]

LGTM