bazel: generate graphql operation interfaces, css module typings

[jbedard]

This replaces #45682 . You can see the fixup commits there for the feedback in that PR.

Test plan

Existing tests

[sourcegraph-bot]

Codenotify: Notifying subscribers in CODENOTIFY files for diff e8aae97...3efc8f8.

Notify	File(s)
@philipp-spiess	client/jetbrains/BUILD.bazel client/jetbrains/webview/BUILD.bazel
@vdavid	client/jetbrains/BUILD.bazel client/jetbrains/webview/BUILD.bazel

[sourcegraph-bot]

Codenotify: Notifying subscribers in OWNERS files for diff e8aae97...3efc8f8.

Notify	File(s)
@sourcegraph/code-exploration-devs	client/wildcard/BUILD.bazel
@vovakulikov	client/wildcard/BUILD.bazel

[sg-e2e-regression-test-bob]

Bundle size report 📦

Initial size	Total size	Async size	Modules
-0.58% (-16.69 kb) 🔽	-0.17% (-25.27 kb) 🔽	-0.07% (-8.58 kb)	0.00% (0)

Look at the Statoscope report for a full comparison between the commits 7405f24 and 749998a or learn more.

Open explanation

• Initial size is the size of the initial bundle (the one that is loaded when you open the page)
• Total size is the size of the initial bundle + all the async loaded chunks
• Async size is the size of all the async loaded chunks
• Modules is the number of modules in the initial bundle

[valerybugakov]

We should address a couple of CI failures before merging:

1. Run prettier over client/shared/dev/generateGraphQlOperations.js
2. Fix the issues with the "Circular type definition of import alias" that blocks many CI jobs.

[jbedard]

This was another thing that was different in one of the operations which we missed.

@kormide was there a reason for changing how this works other then removing duplication?

[kormide]

The changes here were to reduce duplication to make it easier to generate one operations file at a time under Bazel. Is the problem the presence of the field which is undefined rather than the field not existing as above?

[jbedard]

The SharedGraphQlOperations interface needs this set to undefined, where all the others have the same value (which was easy to miss when refactoring it).

[valerybugakov]

Nice!

[valerybugakov]

Should the error message here be different from the generateSchema script?

[jbedard]

I don't really know the terminology enough to say. Did you have a preference?

[valerybugakov]

Ah, sorry. Here's what I mean: in the generateSchema script, the error message Usage: <schemaName> makes sense because we expect one CLI argument — schemaName. It would be nice to update the error message here to match the expected argument list. Does it make sense?

sourcegraph/client/shared/dev/generateSchema.js

Lines 53 to 60 in 25377f2

	async function main(args) {
	if (args.length !== 1) {
	throw new Error('Usage: <schemaName>')
	}
	const schemaName = args[0]
	await generateSchema(schemaName)
	}

[jbedard]

I've added <outputPath> which I think is enough?

[valerybugakov]

Thank you!