Update omni lock deployment and signing message hash

[XuJiandong]

PR: cryptape/omnilock#2
Also update the description of message signing hash.

[Flouse]

Suggestion

omni_lock is deployed using Type ID which means it is upgradable.

Do you think it would be better to guide the developers to query the latest out_point:{ tx_hash, index} of the omnilock code using the get_cells RPC in this RFC? So that the dApps using omnilock don't need to update the latest out_point.tx_hash in their code when omnilock is upgraded.

Examples

Get the latest omnilock code cell on CKB mainnet

curl --location --request POST 'https://mainnet.ckb.dev/' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "id": 2,
    "jsonrpc": "2.0",
    "method": "get_cells",
    "params": [
      {
        "script": {
            "code_hash": "0x00000000000000000000000000000000000000000000000000545950455f4944",
            "hash_type": "type",
            "args": "0x855508fe0f0ca25b935b070452ecaee48f6c9f1d66cd15f046616b99e948236a"
        },
        "script_type": "type"
      },
      "asc",
      "0x1"
    ]
  }'

Get the latest omnilock code cell on CKB testnet

curl --location --request POST 'https://testnet.ckb.dev/' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "id": 42,
    "jsonrpc": "2.0",
    "method": "get_cells",
    "params": [
      {
        "script": {
            "code_hash": "0x00000000000000000000000000000000000000000000000000545950455f4944",
            "hash_type": "type",
            "args": "0x761f51fc9cd6a504c32c6ae64b3746594d1af27629b427c5ccf6c9a725a89144"
        },
        "script_type": "type"
      },
      "asc",
      "0x1"
    ]
  }'