[⭐] Coding challenges for web3 challenges

[bkimminich]

Those web3 hacking challenges that originate from a security flaw in their smart contract implementation, should receive a corresponding coding challenge. This requires:

• Adding the original smart contracts to the codebase so they can be parsed as code snippets (for "Find It" phase)
• Adding 3-4 possible fix options each (for "Fix It" phase)

Adding the original smart contracts might best be done by auto-copying them over from https://github.com/juice-shop/web3-contracts/tree/dev/contracts every time they change there, and also have the vuln-marker comments over there so we do not end with redundant maintenance.

[bkimminich]

Added copy job https://github.com/juice-shop/web3-contracts/actions/workflows/update-contract-snippets.yml that currently fails due to tokens of @JuiceShopBot not working or wrongly configured works fine!

Copies are available and already contain markers for the vulnerable, neutral and to-hide lines of code. The lines were selected based on my understanding, so they might be off by quite a bit - @rishabhkeshan, could you take a look if these are the right lines and if not change the markers in https://github.com/juice-shop/web3-contracts?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. 📆 It will be closed automatically in one week if no further activity occurs.