Add diagnostics and handle errors gracefully / Upgrade Cairo.

[wawel37]

Please, during review check if the speed of diagnostics during doc generation is acceptable.

[maciektr]

Hi!

I've managed to run some benchmarks. For openzeppelin/cairo-contracts I get:

Test run	Time
Without diagnostics	366 ms
With diagnostics	8.37 s
With diagnostics, without lowering group	5.48 s

I tried to run parallel diagnostics warmup (inspired with https://github.com/starkware-libs/cairo/blob/e4136a412b03aff3ba1dec3eb8d8d22356cd67ae/crates/cairo-lang-compiler/src/diagnostics.rs#L220), but it didn't really help to bring the time down at all, resulting in 6.7 s (without lowering group).

Please note that compilation of the cairo-contracts project takes about 22 s.

Given that, the cost of running diagnostics is obviously high, but nothing concerning. We should do that.

I would opt for trying to expose an API in the compiler repository, that does not require LoweringGroup, as adding it to the ScarbDocDatabase even if we don't use it seems quite uncalled for.

[wawel37]

A PR was created in Cairo repository, to extend the API of diagnostics, so the LoweringGroup will no longer be required

[maciektr]

I've tried hard to find some input which would result in diagnostics, and this caused it

            #[starknet::contract]
            pub(crate) mod DualCaseERC20Mock {
                use starknet::ContractAddress;

                component!(path: ERC20Component, storage: erc20, event: ERC20Event);

                #[storage]
                pub struct Storage {
                    #[substorage(v0)]
                    pub erc20: ERC20Component::Storage
                }

                #[event]
                enum Event {
                    #[flat]
                    ERC20Event: ERC20Component::Event
                }
            }

Do you think we should have a test case like that? 🤔

[wawel37]

I've tried hard to find some input which would result in diagnostics, and this caused it

            #[starknet::contract]
            pub(crate) mod DualCaseERC20Mock {
                use starknet::ContractAddress;

                component!(path: ERC20Component, storage: erc20, event: ERC20Event);

                #[storage]
                pub struct Storage {
                    #[substorage(v0)]
                    pub erc20: ERC20Component::Storage
                }

                #[event]
                enum Event {
                    #[flat]
                    ERC20Event: ERC20Component::Event
                }
            }

Do you think we should have a test case like that? 🤔

Done

[maciektr]

Great stuff!
Minor comments attached below.