chore: add preparation commit command pnpm adorno

[3esmit]

Description

Fixes #19

Checklist

Ensure you completed all of the steps below before submitting your pull request:

• Added natspec comments?
• Ran forge snapshot?
• Ran pnpm gas-report?
• Ran pnpm lint?
• Ran forge test?
• Ran pnpm verify?

[0x-r4bbit]

There could be an argument that removing forge test here is not ideal, but on the other hand, this will then latest fail during CI when there's failing tests. So I think it's fine, but I still wanted to point it out.

[3esmit]

forge test is implicit on forge snapshot and pnpm gas-report.

[0x-r4bbit]

@3esmit FYI: if you still want to rename this commit message, you can still do it and then merge (or merge right away)

[3esmit]

I cant merge this, button is grayed out.

[0x-r4bbit]

@3esmit the reason it's grayed out is because your commits are signed.
You might want to set up GPG for this: https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits

[0x-r4bbit]

Also, tip for the future:

We probably don't want to merge main into developing branches.
The developing branches should always be rebased on top of main, and then get merged into main.

That avoids us introducing these merge commits: e1f6eb1

[0x-r4bbit]

@3esmit FYI: I've rebased your adorno commit on top of latest main so this can be merged fast-forward.

[3esmit]

I don't mind, just want to understand the reason behind putting adorno as last command in package.json instead of how I left?

[0x-r4bbit]

@3esmit Ah, no particular reason. There was a merge conflict as there was the release command and the adorno command both modifying the same line in package.json.

I just resolved the conflict without paying much attention to the order of the commands.
Feel free to change this.