This warning was added in 9a2b35e to
try and help reduce confusion if the spec contains targets and therefore
we skip loading other targets.

As it turns out, its a bit overzealous if you specfy anything in the
`targets` section:

    8 warnings found (use docker --debug to expand):
     - Skipping loading of built-in target "bullseye" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "mariner2" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "azlinux3" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "windowscross" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "bionic" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "focal" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "noble" since it is not in the list of targets in the spec
     - Skipping loading of built-in target "bookworm" since it is not in the list of targets in the spec

This is probably more confusing and will just git bigger as we add
support for more things.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

* docs: fix apt repo example

Apt repo keys are required to be readable by a non-root user.
By default http sources have 0o600 permissions which will cause an error
when trying to read the repo.

We didn't see this when creating this example because the above
mentioned error did not directly cause a non-zero exit code.
Instead it only caused an issue if the package you are trying to install
is only available in that repo AND is not cached locally already.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

* docs: Improve targets description

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

* docs: Fix bad copy/paste for some artifact default permissions

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

* README: Add link to supported targets

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

---------

Signed-off-by: Brian Goff <cpuguy83@gmail.com>

Bumps [golang.org/x/crypto](https://github.com/golang/crypto) from 0.27.0 to 0.31.0.
- [Commits](golang/crypto@v0.27.0...v0.31.0)

---
updated-dependencies:
- dependency-name: golang.org/x/crypto
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Bumps [nanoid](https://github.com/ai/nanoid) from 3.3.7 to 3.3.8.
- [Release notes](https://github.com/ai/nanoid/releases)
- [Changelog](https://github.com/ai/nanoid/blob/main/CHANGELOG.md)
- [Commits](ai/nanoid@3.3.7...3.3.8)

---
updated-dependencies:
- dependency-name: nanoid
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <support@github.com>

Mounts were using the destination path as the source name when
generating a source, this made it so mounts would only work correctly if
mounted at the root of the filesystem since source names generally should
not have path separators.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>