### Bug Description `snapcraft` on `latest/` recently removed support for core18 bases. When building such a snap with these releases of `snapcraft` I would expect an error very early on during builds. However, the error instead occurs somewhere else and incorrectly attributes build failures to the plugin I've chosen, rather than the base. This is, of course, not true; the (for example) nil plugin *is* supported by `base: core18` snaps, I'm just not using a version of `snapcraft` which supports building such snaps. ### To Reproduce ``` snap install --channel=latest/edge snapcraft mkdir test-snap && cd test-snap snapcraft init sed -i 's/core22/core18/' snap/snapcraft.yaml snapcraft --use-lxd ``` ### Environment Running at least snapcraft rev 9410, but any sufficiently recent release beyond 7.4.3 will probably exhibit this behavior -- using 7.x risks still works. Running on Ubuntu 23.04 using LXD as the build provider. ### snapcraft.yaml ```shell name: my-snap-name # you probably want to 'snapcraft register <name>' base: core18 # the base snap is the execution environment for this snap version: '0.1' # just for humans, typically '1.2+git' or '1.3.2' summary: Single-line elevator pitch for your amazing snap # 79 char long summary description: | This is my-snap's description. You have a paragraph or two to tell the most important story about your snap. Keep it under 100 words though, we live in tweetspace and your description wants to look good in the snap store. grade: devel # must be 'stable' to release into candidate/stable channels confinement: devmode # use 'strict' once you have the right plugs and slots parts: my-part: # See 'snapcraft plugins' plugin: nil ``` ### Relevant log output ```shell dilyn@Ares:~/tt -> snapcraft --use-lxd Starting Snapcraft 7.4.1.post31+gitf5b2f2e0 Logging execution to '/home/dilyn/.local/state/snapcraft/log/snapcraft-20230629-214349.990383.log' Launching a container. Waiting for container to be ready Waiting for network to be ready... snap "core18" has no updates available The plugin 'nil' does not support snaps using base 'core18'. Run the same command again with --debug to shell into the environment if you wish to introspect this failure. ``` ``` ### Additional context _No response_