fix: handle modern package.json workspace formats

[MrChrisRodriguez]

Handle both legacy format (workspaces as array) and modern (workspaces as object with packages property) formats within package.json.

Example:

  "workspaces": {
    "packages": ["apps/*", "libs/*", "growth/*"],  // <-- this
    "catalog": {
      "@cloudflare/workers-types": "^4.20250619.0",
      // ... other dependency versions
    }
  }
}

[theoephraim]

This looks great. I added a small suggestion just to use lodash utils, mostly just to match the style of the rest of the codebase...

Do you know which package managers support this? Digging through docs, it's not mentioned anywhere:

• https://docs.npmjs.com/cli/v11/using-npm/workspaces
• https://bun.sh/docs/install/workspaces
• https://yarnpkg.com/features/workspaces#how-are-workspaces-declared
• https://docs.deno.com/runtime/fundamentals/workspaces/#npm-and-pnpm-workspace-compatibility

The only place I found it was here - https://bun.com/docs/install/catalogs#1-define-catalogs-in-root-package-json

I hope the other package managers adopt it too - using catalogs (via pnpm) has been great :)

[theoephraim]

Suggested change

	if (Array.isArray(possiblePackagePatterns)) {
	if (_.isArray(possiblePackagePatterns)) {

[theoephraim]

Suggested change

	} else if (possiblePackagePatterns && typeof possiblePackagePatterns === 'object' && possiblePackagePatterns.packages) {
	} else if (_.isObject(possiblePackagePatterns) && _.isArray(possiblePackagePatterns.packages)) {