Deployment of branches not configured for deployment on project

[xantrix]

Describe the bug

Few customers reported that branches not configured for deployment (not present in the branches regex string) are deployed anyway

Expected behavior

honor the branches string regex for deployments

[Schnitzel]

after some research it seems this only happens for environments that have been created in the past and then deleted. The new DeployTarget Logic doesn't check that the environment has already been deleted and just creates it again.
I think this happens here:

lagoon/node-packages/commons/src/deploy-tasks.ts

Line 210 in e08be8e

const apiEnvironment = await getEnvironmentByName(branchName, projectId);

[vincenzodnp]

@shreddedbacon the same happens with the PR regex.
For example, setting it to false allows the creation of environments based on a PR regardless of the PR regex.
ps: the regex envs didn't exist before, so they are brand-new envs