Revert parseArgs change

[bluwy]

Changes

fix #11731

Did a manual revert by hand since there's some good refactors that were made in #11645:

• Full revert of create-astro, @astrojs/db, and @astrojs/upgrade (uses args or yargs-parser)
• Partial revert in astro (uses args-parser), some non-breaking refactors were kept.
• Other internal scripts are kept using parseArgs as they don't affect us as much.

Explanation of problem

With our previous option, parseArgs parse things rather strangely:

pnpm dev --host --port 1234
=> values: { 'host': '--port' }, positionals: [..., '1234']

pnpm dev --port 1234 --host
=> values: { 'port': true, 'host': true }, positionals: [..., '1234']

pnpm dev --port 1234 --open --host
=> values: { 'port': true, 'open': '--host' }, positionals: [..., '1234']

pnpm dev --host --port
=> values: { 'host': '--port' }, positionals: [...]

I also tested enabling strict: true, but things get sillier since parseArgs doesn't support dual boolean/string arguments. I also feel like it'll cause more problems for the other packages so I reverted them all back. Why can't node design proper APIs :(

Testing

Tested manually. The cli.test.js should also pass.

Docs

n/a. bug fix.

[changeset-bot]

🦋 Changeset detected

Latest commit: eed0b49

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR