unsupported interpolation for COMPOSE_PROJECT_NAME

[europ]

Describe the bug
podman-compose does not support interpolation for COMPOSE_PROJECT_NAME variable - anywhere in compose file.

To Reproduce

1. Create docker-compose.yml

name: custom_project-name
services:
  test:
    container_name: '${COMPOSE_PROJECT_NAME}-test'
    image: container-registry.oracle.com/os/oraclelinux:8-slim
    command:
      - sleep
      - "5"

1. Run podman-compose up

Expected behavior

# created container

Actual behavior

Error: running container create option: names must match [a-zA-Z0-9][a-zA-Z0-9_.-]*: invalid argument
[test] | Error: unknown shorthand flag: 't' in -test
[test] | See 'podman start --help'

Output

$ podman-compose version
podman-compose version 1.2.0
podman version 5.2.5

$ podman-compose up
Error: running container create option: names must match [a-zA-Z0-9][a-zA-Z0-9_.-]*: invalid argument
[test] | Error: unknown shorthand flag: 't' in -test
[test] | See 'podman start --help'

Environment:

• OS: Mac
• podman version: 5.2.5
• podman compose version: 1.2.0

Additional context

• value for COMPOSE_PROJECT_NAME is loaded correctly

  podman-compose/podman_compose.py

  Line 1903 in 4ae6ccb

  if not project_name:

• https://docs.docker.com/reference/compose-file/interpolation/

• https://docs.docker.com/compose/how-tos/environment-variables/envvars/

• https://docs.docker.com/reference/compose-file/version-and-name/#name-top-level-element

• https://github.com/compose-spec/compose-spec/blob/main/04-version-and-name.md

  Name top-level element
  
  The top-level name property is defined by the Specification as the project name
  to be used if you don't set one explicitly. Compose offers a way for you to override
  this name, and sets a default project name to be used if the top-level name element 
  is not set.
  
  Whenever a project name is defined by top-level name or by some custom
  mechanism, it is exposed for interpolation and environment variable resolution
  as COMPOSE_PROJECT_NAME