refactor: forc-node as lib

[zees-dev]

Description

This PR fundamentally refactors the forc-node plugin architecture by embedding the Fuel Core node directly as an in-process library rather than spawning it as a subprocess.
This architectural change modernizes the forc-node plugin and lays the groundwork for advanced local development features.

🔄 Changes Overview

Core Architectural Changes

• In-Process Execution: Fuel Core now runs within the same process as the plugin, eliminating subprocess management overhead
• Direct Integration: Replaced subprocess spawning with direct library calls to fuel-core
• Unified Logging: Consolidated logging and error handling across all execution modes
• Improved Configuration: Enhanced configuration display and management for better debugging

Dependency Updates

• Added direct fuel-core dependencies
• Added fuel-core-chain-config for configuration management
• Integrated tracing and tracing-subscriber for improved logging
• Updated Cargo.lock with necessary transitive dependencies

💡 Motivation

Current Limitations

• Subprocess management adds complexity and potential failure points
• Limited ability to extend node functionality
• Difficult to implement advanced features like state forking (planned feature)

Benefits of This Change

1. Performance: Eliminates IPC overhead and reduces startup time
2. Reliability: Direct function calls are more reliable than subprocess communication
3. Extensibility: Easier to add advanced features in future PRs

Checklist

• I have linked to any relevant issues.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation where relevant (API docs, the reference, and the Sway book).
  • If my change requires substantial documentation changes, I have requested support from the DevRel team
• I have added tests that prove my fix is effective or that my feature works.
• I have added (or requested a maintainer to add) the necessary Breaking* or New Feature labels where relevant.
• I have done my best to ensure that my PR adheres to the Fuel Labs Code Review Standards.
• I have requested a review from the relevant team or maintainers.