Migration of linea-tracer into linea-monorepo

[jonesho]

🔐 🔐 Should this be a security advisory instead? 🔐 🔐

Description

As part of the effort to consolidate various besu plugins (e.g. sequencer, tracer, etc..) into linea-monorepo and streamline their releases, this issue is for migrating linea-tracer into linea-monorepo while keeping minimal friction for arithmetization team to commit, test, and release.

Motivation

From Julien

The tracer, sequencer, and besu nodes are built by many people in different teams. Yet the full process is very heterogeneous and tedious, spreads across multiple repos, few people (if any) understand it end to end and feel owner of the process. Yet, it's our most critical component. Reorganizing the teams isn't the solution as these components naturally spreads across teams ; some parts of the code are only understood by a single person.

First step here is to migrate linea-tracer into linea-monorepo with the necessary Github pipeline integrations

Tasks

• Migrate linea-tracer code base to a subfolder (e.g. under ./besu-plugins) in our linea-monorepo repo
• Integrate our GHA pipeline to run tests when relevant changes are committed
• Add manual GHA release workflow for linea-tracer plugin

Acceptance criteria

• List tests that need to be implemented or checks to consider this task completed.

Risks

• These are risks that may prevent completion of the task as well as areas to pay special attention to

Remember to

• Add the documentation label in case there is an impact on the documentation
• Add priority and team labels
• Add Task for updating the Runbook or adding/updating existing metrics and alerts.