Handle new strate transition bytecode and new consensus parameter version

[acerone85]

on on upgrade transaction

Closes #2584

Questions for the reviewers:

• I am assuming that the latest known state transition bytecode version and latest known consensus parameters versions will be loaded from the storage when the global root service starts, and will be passed to the proces_block function through the UpdateMerklizedTables trait. Is this reasonable?
• I am revalidating the upgrade transaction metadata, but I am not sure if this is needed?
• I am assuming that both state transition bytecode version and consensus parameters version increment by 1 when an upgrade transaction with the corresponding purpose is processed, is this correct?

Linked Issues/PRs

Description

Checklist

• Breaking changes are clearly marked as such in the PR description and changelog
• New behavior is reflected in tests
• The specification matches the implemented behavior (link update PR if changes are needed)

Before requesting review

• I have reviewed the code myself
• I have created follow-up issues caused by this PR and linked them here

After merging, notify other teams

[Add or remove entries as needed]

• Rust SDK
• Sway compiler
• Platform documentation (for out-of-organization contributors, the person merging the PR will do this)
• Someone else?