Explicitly use package.json for functions typegen

[nickwesselman]

WHY are these changes introduced?

Workaround for unexpected behavior in graphql-config.

If a developer has a root .graphqlrc or similar in their app, typegen fails with an error such as

ENOENT: no such file or directory, scandir './sample-apps/discounts/extensions'

WHAT is this pull request doing?

Explicitly pass --config package.json to graphql-code-generator. This makes us more opinionated but matches the structure of our boilerplate. I don't have a known use case at the moment which would require customizing this.

How to test your changes?

• Attempt typegen against a JavaScript function in our examples repo, e.g. product-discount-js

• The same is successful using a local build of this PR

pnpm shopify app function typegen --path ~/src/function-examples/sample-apps/discounts/extensions/product-discount-js

[github-actions]

We detected some changes at either packages/*/src or packages/cli-kit/assets/cli-ruby/** and there are no updates in the .changeset.
If the changes are user-facing, run "yarn changeset add" to track your changes and include them in the next release CHANGELOG.

[github-actions]

Coverage report

St.❔	Category	Percentage	Covered / Total
🟡	Statements	72.64% (-0.12% 🔻)	4161/5728
🟡	Branches	69.98% (-0.28% 🔻)	1881/2688
🟡	Functions	69.78% (-0.03% 🔻)	1099/1575
🟡	Lines	73.94% (-0.1% 🔻)	3973/5373

Show files with reduced coverage 🔻

St.❔	File	Statements	Branches	Functions	Lines
🔴	... / app-command.ts	0%	0% (-100% 🔻)	0%	0%
🟢	... / ui.tsx	95.83%	57.14% (-7.14% 🔻)	100%	95.65%
🟢	... / base-command.ts	87.93% (+1.49% 🔼)	83.33% (-3.51% 🔻)	87.5% (+7.5% 🔼)	90.2% (+1.73% 🔼)
🟡	... / output.ts	68.81% (-3.67% 🔻)	64.41% (-3.39% 🔻)	62.79% (-2.33% 🔻)	69.9% (-2.91% 🔻)

Test suite run success

1075 tests passing in 535 suites.

Report generated by 🧪jest coverage report action from a8720bd