feat: Split Launchpad Contract into p/r Pacakges

[notJoon]

Description

WIP

[notJoon]

@moul

I am currently working on separating the launchpad contract into p and r packages based on their states. As you mentioned earlier, I've structured the two packages to have identical names and added files as needed.

The goal of this refactor is:

1. re-structuring to make it easier to apply upgradable realm patterns (separation of p and r based on their status)
2. reduce dependencies
3. enhance code reusability and maintainability

Although this PR still in WIP, could you please check if this is the structure you had in mind? Thank you.

Please note this: there is duplicate code since I have only migrated the types and pure functions, and have not yet refined r/launchpad directory.

cc: @dongwon8247

[sonarqubecloud]

Quality Gate passed

Issues
18 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
5.8% Duplication on New Code

See analysis details on SonarQube Cloud

[moul]

if you think that the r/launchpad/v2 will be able to reuse most of the p/launchpad, then it could make sense to make this split, but if not, it's probably better to keep most of the logic in a single r/launchpad.