chore(main): release 0.9.0

[github-actions]

🤖 I have created a release beep boop

0.9.0 (2023-06-04)

Features

• all: check L1 reorg before each operation (#252) (e76b03f)
• all: rename treasure to treasury (#233) (252959f)
• all: update protocol bindings and some related changes (#237) (3e12042)
• bindings: update bindings with EthDeposit changes (#255) (f91f2dd)
• bindings: update go contract bindings (#243) (132500e)
• driver: optimize reorg handling && add more tests (#256) (20c38a1)
• pkg: do not return error when genesis block not found (#244) (8033e31)
• proof_producer: update request parameters based on new circuits changes (#240) (31521ef)
• proposer: add a --minimalBlockGasLimit flag to mitigate the potential gas estimation issue (#225) (ab8305d)
• proposer: add a new metric to track block fee (#224) (98c17f0)
• proposer: propose multiple L2 blocks in one L1 block (#254) (36ba5db)
• prover: add --expectedReward flag (#248) (f64a762)
• prover: improve proof submission delay calculation (#249) (7cc5d54)
• prover: normal prover should wait targetProofTime before submitting proofs (#232) (2128ddc)
• prover: remove submission delay when running as a system prover (#221) (49a25dd)
• prover: remove the unnecessary special proof delay (#226) (dcead44)
• prover: updates based on protocol proofTimeTarget changes (#227) (c6ea860)
• repo: enable OpenAI-based review (#235) (88e4dae)

Bug Fixes

• driver: handle reorg (#216) (fc2ec63)
• flag: add a missing driver flag to configuration (#246) (0b60243)
• prover: fix an issue in prover event loop (#257) (c550f09)
• prover: update bindings && fix a delay calculation issue (#242) (49c3d69)
• repo: fix openAI review workflow (#253) (f44530b)

---

This PR was generated with Release Please. See documentation.

[github-actions]

Overall, this looks like a well-structured pull request. I have the following feedback:

• Make sure to include a description of the changes in the commit message and CHANGELOG.md.
• The renaming of treasure to treasury should be mentioned in the commit message and CHANGELOG.md.
• The changes to the proof_producer should also be included in the commit message and CHANGELOG.md.
• Make sure to add comments to the code changes that explain why they were made and what they do.
• Consider using descriptive variable names instead of repeating variables (e.g. a and b).

[github-actions]

🤖 Release is at https://github.com/taikoxyz/taiko-client/releases/tag/v0.9.0 🌻