updated near-primitives and associated crates

[anthony-near]

needed for releasing the relayer used for meta transactions near/pagoda-relayer-rs#1 and cli changes near/near-cli-rs#151

• update near-primitives and associated crates to 0.16.0
• downgrade tokio to 1.19.0 to be compatible with near-primitives subdependency versions of tokio
• fix signature type bug introduced in jsonrpc: simplify params representation nearcore#8460
• updated error msg str - see updated near-primitives and associated crates #122 (comment)
• bump rust-version to 1.67.1 after toolchain: update to 1.67.1 nearcore#8456.

[miraclx]

Contextual CI error:

thread 'methods::query::tests::test_contract_execution_error' panicked at 'this is unexpected: ServerError(
    HandlerError(
        ContractExecutionError {
            vm_error: "wasm execution failed with error: MethodResolveError(MethodEmptyName)",
            block_height: 63503911,
            block_hash: 4vMwedjLwTvGGzW23qJQrbaPmNKxQ3xetKXm6s1o8isP,
        },
    ),
)', src/methods/query.rs:175:9

Looks like near/nearcore#7815 changed things a bit. And got rid of the VMResult enum that encapsulated the VMOutcome + VMError. And instead just unwrapped that into a Result from which a VMOutcome is unwrapped.

For this reason, the string inside the outcome report has changed a little.

-wasm execution failed with error: FunctionCallError(MethodResolveError(MethodEmptyName))
+wasm execution failed with error: MethodResolveError(MethodEmptyName)

@anthony-near, can you update the following lines to exclude the FunctionCallError(..) wrap:

1. near-jsonrpc-client-rs/src/methods/query.rs

   Line 117 in 18b998b

   }) if vm_error.contains("FunctionCallError(MethodResolveError(MethodNotFound))")

2. near-jsonrpc-client-rs/src/methods/query.rs

   Line 182 in 18b998b

   }) if vm_error.contains("FunctionCallError(MethodResolveError(MethodEmptyName))")