Finalize and document instructions for migrating libraries into core monorepo

[MajorLift]

Overview

As part of Shared Libraries Q3/Q4 OKRs, the team would like to document a process guide for migrating libraries into this monorepo.

This entails two tasks:

1. The process needs fine-tuning. During the course of migration efforts utilizing the initial instructions (Migrate libraries into core monorepo #1079 (comment)), several blockers, points of caution, and gaps were identified. These issues need to be resolved and the solutions documented.

2. The lessons and solutions from the initial migrations need to be compiled into a step-by-step guide that is granular and streamlined enough to be easily followed by the team (and potentially external contributors) to migrate any library into the core monorepo without significant adjustments or delays.

Tasks

1. Fill in the blanks

• Implement script for prepending package names when porting release tags : Add script for tag porting when migrating libraries into the core monorepo #1800.
• Modify auto-changelog validator to handle inconsistent package-name prefixes in the ported tags of renamed packages: Package Rename Changelog Validation #1795.
• WONTFIX: The entire commit history of the core repo is included in all diffs between migrated commits and commits made after the target package's git history is merged into the monorepo.
• Solution for migrating issues and PRs from the original repo into the monorepo: Explore solutions for transferring issues and PRs from other repos into the core monorepo #1835
• Add option in create-release-branch tool to specify the last release tag name for a given subpackage: Add option to specify last release tag name for core subpackages create-release-branch#105
• Enable autochange-log validator to handle manually created tags (for release commits that were untagged in the original repo): Add missing json-rpc-{engine,middleware-stream} CHANGELOG tag diff links #2008
• Enable GH Pages workflows for publishing docs in core monorepo so that existing docs from migration target can be published under core/ namespace: Configure GitHub Pages workflows for publishing docs #1845

2. Documentation

• Break down each step into granular, orthogonal PR groupings and define the best order for executing these tasks: Fully migrate eth-json-rpc-provider into core monorepo  #1551 (comment).
• Compile a comprehensive, standardized process guide: Document migration process for libraries moving to core monorepo #1832.

[MajorLift]

Closed by #2071