0.5.0 spec

[marioiordanov]

Changes

Test module spec_reader

For generating JSON requests and responses from JSON-RPC specification.
edit_spec_instructions.yaml file is used for correcting some errors in the spec and removing some PENDING structs, because we dont support pending feature yet
NOTE: If for some reason there are unwraps in this module, keep in mind that its only used in tests.
NOTE: the specs in test_data are not 100% similar to the the spec in starkware repo, due to limitation of modifying the spec some irrelevant data to devnet was removed manually

• ApiError::ContractError receives an Error as parameter. Serializing ContractError to RpcResult populates the data object.
• Added .cargo/config.toml with entries - RPC_SPEC_VERSION, STARKNET_VERSION
• Removed starknet_pendingTransactions
• Added starknet_specVersion
• Removed method StarknetTransaction::create_rejected
• Made StarknetTransaction::finality_status member field non-optional
• Added starknet_getTransactionStatus RPC method
• Added starknet_version and l1_gas_price
• Added execution_resources to receipt
• Decorate most of the input/output structs with deny_unknown_fields, so we can be maximally compliant with the specification.
• Removed PatriciaKeyHex and moved its serialization/deserialization to Starknet-types
• Removed data.rs file
• Adapted test_simulate_transactions.rs
• Extracted resource fee costs names into constants.rs
• Added conversion from StateDiff to ThinStateDiff
• Refactor StateUpdate to hold StateDiff, instead of its flattened properties
• Added some TODOs which should be handled by this issue: JSON-RPC methods returning extra properties not in the spec #248
• Added Deserialize or Serialize to some structs in so they can be tested with the spec_reader.
• All endpoints read/write now return StarknetResponse enum, which has an entry for every method. It is used for being able to match if generated response from spec_generator can be deserialised to the implemented one.
• Refactor api_error_to_rpc_error
• Wrap write_endpoints.rs methods input params into enums in the form BroadcastedDeclareTransactionEnumWrapper for specifying the type, because before only accepting BroadcastedDeclareTransaction doesn't accept a type field, but in the spec a type field is specified for all input objects for the methods addDeclareTransaction, addInvokeTransaction, addDeployAccountTransaction
• Implemented logic for calculating ExecutionResources in transaction receipt
• Remove abi field when deserializing to Sierra contract class, If the field is empty.
• Removed some irrelevant for 0.5.0 test_data files - declare_accepted.json and invoke_accepted.json
• Refactored message_available_if_estimation_panics to send custom rpc request, instead of using starknet-rs, because with 0.5.0 the data field of the error result is populated with information and in this test we need to check the revert reason returned from the rpc request

Checklist:

• Created git tag json-rpc-0.4.0 on main just before this PR is merged
• Applied formatting - ./scripts/format.sh
• No linter errors - ./scripts/clippy_check.sh
• Performed code self-review
• Rebased to the last commit of the target branch (or merged it into my branch)
• Documented the changes
• Linked the issues which this PR resolves
• Checked the TODO section in README.md if this PR resolves it
• Updated the tests
• All tests are passing - cargo test

[FabijanC]

I've reviewed everything except the spec_reader testing module, I would like to consult with you about that.