platformatic: `.env` files in services/* directory breaks runtime start

In a Platformatic Runtime, if thre is a .env file inside a service directory, seems like it is loaded in place of the root .env one. This happens only if the service’s platformatic.json file contains a reference to an env variable like

{
  "plugins": {
    "typescript": "{PLT_MY_SERVICE_TYPESCRIPT}"
  }
}

Repro:

$ node packages/create-platformatic/create-platformatic.mjs

Select Application and create the first (and only service)

Once finished ensure that the runtime starts correctly and stop it. Then

$ cd $RUNTIME_ROOT_DIR
$ touch services/YOUR_SERVICE_NAME/.env

Start again and you’ll see that an error occurs, complaining that an env variable is missing.

The .env file inside the service should be either ignored or loaded together with the root one