🚧 Dev ➾ Adjust LIGO default parameter/storage list files to use explicit types

🔗 Epic|Feature Link

No response

🚥 Definition of Done

[X] 🎯 Planning and Design
[ ] 🏎️ Dev Implementation Complete
[ ] ♾️ PR Merged
[ ] 🏆 Product Acceptance

🧰 Work Description

LIGO will not work in many cases when a variable in the storage or parmeter list files are not explicitly typed.

As such, we need to update our examples to have explicit types, and too adjust some of the messaging. For instance, the default content for the storage/parameter list includes the following comments:

// If your storage is a simple value, you can define it directly
// E.g. let storage = 10
//
// For added type-safety, you can reference the type of your storage from the contract
// E.g. let storage : Contract.storage = 10

We should instead adjust this to be:

// IMPORTANT: We suggest always explicitly typing your storage values:
// E.g.: `let storage: int = 10` or `let storage: Contract.storage = 10`

✅ To Do

[ ] Adjust default content for storage/parameter list files for LIGO to use explicit types when defining values
[ ] Adjust the default content comments as dictated above

⚖️ Acceptance Criteria

✨ Functional:

[ ] When generating default content for each permutation, all values should use explicit types
[ ] When generating default content for each permutation, we should see the updated comment

🔭 Scope