Validate flags used in `kbuild.toml`

[Baltoli]

In runtimeverification/mir-semantics#291, I noticed that specifying an unsupported flag in kbuild.toml will silently succeed, rather than giving any kind of warning or error that the flag isn't actually being used.

We should check for such cases and report them at build time.

[gtrepta]

I see some duplication between these two related parameter lists. Could we instead have kbuild rely on kompile to define what flags are available and validate them?

pyk/src/pyk/ktool/kompile.py

Lines 320 to 331 in f9a2da5

	class KompileArgs:
	main_file: Path
	main_module: str | None
	syntax_module: str | None
	include_dirs: tuple[Path, ...]
	md_selector: str | None
	hook_namespaces: tuple[str, ...]
	emit_json: bool
	gen_bison_parser: bool
	bison_parser_library: bool
	post_process: str | None
	read_only: bool

pyk/src/pyk/kbuild/project.py

Lines 60 to 82 in f9a2da5

	class Target:
	name: str # TODO Maybe remove name and store in project as Dict
	main_file: Path # relative to source folder
	backend: KompileBackend
	main_module: str | None
	syntax_module: str | None
	md_selector: str | None
	hook_namespaces: tuple[str, ...] | None
	emit_json: bool | None
	gen_bison_parser: bool | None
	bison_parser_library: bool | None
	# LLVM backend
	opt_level: int | None
	ccopts: tuple[str, ...] | None
	no_llvm_kompile: bool | None
	enable_search: bool | None
	enable_llvm_debug: bool | None
	llvm_kompile_type: LLVMKompileType | None
	llvm_kompile_output: str | None
	# Haskell backend
	concrete_rules: tuple[str, ...] | None
	haskell_binary: bool | None

[gtrepta]

I just drafted a PR with my proposed solution #792