[FEAT]: Add missing .tool-versions in contracts and scripts

[danielcdz]

📘 Description

Some directories containing scripts and contracts are missing the .tool-versions file. This file is crucial for specifying the versions of dependencies, making it easier for users to know which versions to use for each case. We want to ensure that all relevant directories include this file for better consistency and user experience.

✅ Acceptance Criteria

• The .tool-versions file is in all relevant script and contract directories.
• The file accurately lists the required versions of dependencies for each case.

🌎 References

• [asdf Documentation](https://asdf-vm.com/)

📜 Additional Notes

• ⚠ Do not apply until the ODBoost begins.
• ⚠ Read our contribution guidelines before applying.

[NueloSE]

A frontend developer with experiences using JavaScript and modern frameworks for creating seamless and interactive user experience. Am also experienced with developing and deploying smart contracts, as well as writing tests to ensure functionality.
Looking through the project I have been able to identify some directory without the .tool-version file. Some of these directory are: hello_world, simple_contract_with_events.

[GideonBature]

May I take care of this?

May I take care of this?

I am a software engineer with working knowledge of Cairo. I will be able to send my first PR in 48 hours.

[Akshola00]

Mind if I try this one?
Can I work on this
I'm confident I can handle this
Pls assign

[SoarinSkySagar]

may i take up this issue @danielcdz ?

background: cairo dev with 5 months of experience and regular contributor at @keep-starknet-strange

eta: 2 days

[raizo07]

Can I work on this, please?

[CollinsC1O]

Hello @danielcdz, I'm a front-end and a blockchain developer and I will love to take on this issue. providing the required solution swiftly.

[Jagadeeshftw]

Proposal to Work on the Issue

I would be delighted to contribute to this issue, as I have extensive experience with Cairo programming and developing decentralized applications on StarkNet.

Estimated Timeline

I anticipate delivering a working solution within the next 24 hours. Please let me know if I can proceed.

Looking forward to contributing and collaborating!

Best regards,
Jagadeesh B

[salazarsebas]

My background

I'm a software engineer and passionate about solving problems, I've been contributing to open source software for a few months and it's an experience that has taught me a lot and I really like to contribute to other projects. I am a member of the Dojo Coding community⛩️. I will dedicate all my effort to complete this issue in the best way.

[GideonBature]

May I take care of this?

I am a software engineer with working knowledge of Cairo, it's toolings like the snforge and sncast as well as their versioning. I will be able to send my first PR in 48 hours.

[ShantelPeters]

Can I try solving this issue?

[wheval]

Could I take over this issue?

[Wendyalbert]

I’d like to work on this.

[salazarsebas]

Hi, thank you very much for the assignment of this issue.
I have just submitted my pr. 📟
If I have to make changes I will do my best to deliver the best result.🫡