port(storage): use the cached block height from the database at the time of creation of the view

[rymnc]

Linked Issues/PRs

• same as chore(storage): use the cached block height from the database at the time of creation of the view #2639, but for master

Description

The most important changes include adding metadata support to the GenericDatabase, modifying type definitions to include height metadata, and updating various methods to use the new database structure.

Database Structure Improvements:

• crates/fuel-core/src/database.rs: Added metadata support to the GenericDatabase and updated type definitions to include height metadata. This includes changes to methods such as new, in_memory, and latest_view. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13]

• crates/fuel-core/src/state.rs: Updated type definitions for IterableKeyValueView and KeyValueView to include height metadata. Modified the TransactableStorage trait to use the new types. [1] [2] [3]

Code Refactoring:

• crates/fuel-core/src/state/generic_database.rs: Refactored the GenericDatabase struct to include metadata and updated various trait implementations to support the new structure. [1] [2] [3] [4] [5] [6] [7]

Performance Improvements:

• crates/fuel-core/src/database.rs: Improved the latest_height method to use metadata for fetching the latest height, enhancing performance.

Test Updates:

• crates/fuel-core/src/service/genesis/importer/import_task.rs: Updated tests to use the new KeyValueView and IterableKeyValueView types with height metadata.

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?