Catch-up on asks from Cadence dev community

[j1010001]

Why (Objective)

We haven't had time to follow-up on requests from Cadence devs in the run-up to Crescendo.
Review language changes/feature requests form Cadence dev community, identify those that would benefit the community.

How will we measure success (Key Results) ?

• Schedule Working group session to discuss known issues with community devs
• Clarify impact and effort for discussed issues.

Effort Estimate

TBD

DACI

Role	Assigned
Driver	Technical: @turbolent, EM: @j1010001
Approver	@dete
Consulted	@roham, @Kay-Zee
Informed	Flow engineering team

Issues identified so far:

• Discuss effort remaining for impl. metering: Add a WebAssembly API #2853
• Immutable contracts on C1.0 (Get community feedback)
• Stretch-goal: Discuss scope / effort for: Direct resources access by ID (requested for long time by many community members)