Add usroverlay --readonly

[evan-goode]

Resolves #2034.

[gemini-code-assist]

Code Review

This pull request adds a --readonly flag to the usroverlay command, allowing the creation of a read-only transient overlay on /usr. The changes are well-implemented across the CLI, the two backends (ostree and composefs), documentation, and tests. The code is clear and the new functionality is tested. I have one minor suggestion to improve code conciseness.

[gemini-code-assist]

This match statement can be simplified into an if/else expression to make it more concise.

Suggested change

	let args = match access_mode {
	// In this context, "--transient" means "read-only overlay"
	FilesystemOverlayAccessMode::ReadOnly => ["admin", "unlock", "--transient"].as_slice(),
	FilesystemOverlayAccessMode::ReadWrite => ["admin", "unlock"].as_slice(),
	};
	let args: &[&str] = if access_mode == FilesystemOverlayAccessMode::ReadOnly {
	// In this context, "--transient" means "read-only overlay"
	&["admin", "unlock", "--transient"]
	} else {
	&["admin", "unlock"]
	};

[cgwalters]

just update-generated should resync the new options

[evan-goode]

Done in a separate commit

[ckyrouac]

not a huge deal but I think these tmt/* changes belong in the previous commit that adds the test code

[evan-goode]

Still want me to squash these? Maybe it's better to keep them separate if the latter commit has unrelated changes from update-generated.

[ckyrouac]

I think this might have been a bad rebase? I believe this should point to the new test-usroverlay.nu file from the previous commit

[evan-goode]

Hmm, just tried just update-generated again over f8eef4a and got an identical diff. Maybe update-generated was not run after #2022 or #1995?

[jeckersb]

Yeah we have #1891 to hopefully gate on update-generated so we don't continue getting into this state where things are out of date. Known problem unfortunately ☹️