### Bug Description Some commands, like clean, should not need such a strict schema validation, if all they gonna do is “clean”. IoW, if I want to `clean` my project, the YAML shouldn't have an impact on the operation. ### To Reproduce Write a bogus rockcraft.yaml and run `rockcraft clean`. ### Environment Any ### rockcraft.yaml ```shell name: my-rock base: ubuntu@22.04 # the base environment for this rock version: '0.1' # just for humans. Semantic versioning is recommended summary: Single-line elevator pitch for your amazing rock # 79 char long summary description: | This is my-rock-name's description. You have a paragraph or two to tell the most important story about it. Keep it under 100 words though, we live in tweetspace and your description wants to look good in the container registries out there. platforms: # the platforms this rock should be built on and run on amd64: some-unsupported-field: foo parts: my-part: plugin: nil ``` ### Relevant log output ```shell Bad rockcraft.yaml content: - extra field 'some-unsupported-field' not permitted in top-level configuration For more information, check out: https://documentation.ubuntu.com/rockcraft/en/stable/reference/rockcraft.yaml ```