Signed-off-by: Nicolas De Loof <[email protected]>

PR #261 changed `docker compose` behavior to require normalized project
names as input, instead of normalizing project names automatically. This
landed in compose-spec/compose-go v1.2.5 and docker/compose v2.5.1.

However, the previous error message gave no indication why a name isn't
valid.  This is surprising for users whose previously working project
names no longer work with newer versions of `docker compose`.

As of compose-spec/compose-spec#314, the spec now contains the text:

> Project name MUST contain only lowercase letters, decimal digits,
> dashes, and underscores, and MUST begin with a lowercase letter or
> decimal digit.

This updated error message provides a concise version of this
requirement based on regular expression character range notation.

See also:

- compose-spec/compose-spec#311
- docker/compose#9741

Signed-off-by: Mike Bland <[email protected]>

This update landed in compose-spec/compose-spec#314, reflecting the new
project name spec:

> Project name MUST contain only lowercase letters, decimal digits,
> dashes, and underscores, and MUST begin with a lowercase letter or
> decimal digit.

Signed-off-by: Mike Bland <[email protected]>

This fixes the failure caught by loader/loader_test.go in the CI run for
PR #362:

```
--- FAIL: TestFullExample (0.00s)
    loader_test.go:969: assertion failed: error is not nil: name Does not match pattern '^[a-z0-9][a-z0-9_-]*$'
```

Signed-off-by: Mike Bland <[email protected]>

Signed-off-by: Laura Brehm <[email protected]>

Add `additional_contexts` to `build` service config

Signed-off-by: Nicolas De Loof <[email protected]>

Signed-off-by: GitHub <[email protected]>

Update compose-spec.json