Update StagingStatusUpdated.code event value to SHA3_256 hash

[sisyphusSmiling]

Closes: #37

---

For contributor use:

• Targeted PR against main branch
• Linked to Github issue with discussion and accepted design OR link to spec that describes this work.
• Code follows the standards mentioned here.
• Updated relevant documentation
• Re-reviewed Files changed in the Github PR explorer
• Added appropriate labels

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 75.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 83.81%. Comparing base (5f45a7f) to head (f165996).

Files	Patch %	Lines
contracts/MigrationContractStaging.cdc	75.00%	1 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #38      +/-   ##
==========================================
- Coverage   83.91%   83.81%   -0.11%     
==========================================
  Files           6        6              
  Lines         342      346       +4     
==========================================
+ Hits          287      290       +3     
- Misses         55       56       +1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[turbolent]

Nice!

Maybe change the parameter code: String of the event StagingStatusUpdated to codeHash: [UInt8; 32] to make the event less stringly typed and reduce the overhead of hex-encoding

[sisyphusSmiling]

Maybe change the parameter code: String of the event StagingStatusUpdated to codeHash: [UInt8; 32] to make the event less stringly typed and reduce the overhead of hex-encoding

Makes sense. cc-ing @bluesign in case his tooling depends on events at all. I think not, but tagging just in case