Add move 2024 Conventions as comments to the new package example

[yanganto]

Description

• Fix typo in 2024 Conventions
• Add Conventions as comments to a new package when sui move new
• Add Conventions link to a new package when sui move new

Test plan

• no extra tests needed

Release notes

• CLI: Add Conventions as comments to a new package when sui move new

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
sui-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Dec 3, 2024 1:15am

3 Skipped Deployments

Name	Status	Preview	Comments	Updated (UTC)
multisig-toolkit	⬜️ Ignored (Inspect)	Visit Preview		Dec 3, 2024 1:15am
sui-kiosk	⬜️ Ignored (Inspect)	Visit Preview		Dec 3, 2024 1:15am
sui-typescript-docs	⬜️ Ignored (Inspect)	Visit Preview		Dec 3, 2024 1:15am

[damirka]

Thank you for your PR @yanganto! It is a fresh and interesting improvement, but I'm afraid filling every new project wit coding conventions may come out as noisy, and instead I suggest changing it to a single line with a link to coding conventions. Let me know if you're comfortable doing that, or we can pick it up some other time.

[yanganto]

For developer experience, they just want to deliver a product with high quality, and do not want anyone to say their code is bad after product shipped.

Previous commit is exactly a new developer will want in my imagine.
"Just tell them what is the best practice clearly without asking a lot of document reading and still ambiguous".

For me, I will not insist on this PR or anything. My current topic is to bring the best practice to developer/new comer, I just try to make this smooth an easier. If there is no real best practice at this moment, it is still fine for me.