Move util/launcher/src/migrate.rs to an independent crate

[eval-exec]

What problem does this PR solve?

This PR want to move util/launcher/src/migrate.rs related module into an independent crate, this will help resolve ckb's dependency cycles issue.

In the production build: ckb-launcher need ckb-chain.
But in dev build: ckb-chain need ckb-launcher's SharedPackage and SharedBuilder.

If we move util/launcher/src/migrate.rs to an independent crate, then SharedPackage and SharedBuilder can be moved to ckb-shared. Then we won't need ckb-launcher to build shared in ckb's unit tests anymore.

On develop branch:

flowchart TD
    subgraph ckb-launcher
        Launcher
        Migrate
    end

Loading

After this PR:

flowchart TD
    subgraph ckb-launcher
        Launcher

    end

    subgraph ckb-migrate
        Migrate
    end
    ckb-launcher --> ckb-migrate

Loading

What's Changed:

Related changes

• Move util/launcher/src/migrate.rs related module into an independent crate (ckb-migrate)

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code ci-runs-only: [ quick_checks,linters ]

Side effects

• None

Release note

Title Only: Include only the PR title in the release note.

[eval-exec]

Fixing cargo clippy...

[EthanYuan]

If we move util/launcher/src/migrate.rs to an independent crate, then SharedPackage and SharedBuilder can be moved to ckb-shared. Then we won't need ckb-launcher to build shared in ckb's unit tests anymore.

Will this PR include moving SharedPackage and SharedBuilder to ckb-shared?

[eval-exec]

Will this PR include moving SharedPackage and SharedBuilder to ckb-shared?

No, this PR only move struct Migrate related code in ckb-launcher crate to a new independent crate (ckb-migrate).

"Moving SharedBuilder and SharedPackage to ckb-shared crate" can be found in next pr: #4236