[Bug]: CI/CD and Deploy to environment fails when dependent to API V2 extension

[MartinFellow]

AL-Go version

7.0

Describe the issue

After updating AL-Go to version 6.4 and also 7.0 we have issues with specific repositories.
The issues seems only to be where we have a dependency to the API V2 extension, my hunch is that its because its an exclude app.
The error shows under the deployment step, see the image below.
It gives an 401 unauthorized error, that does not make sense at all.

I have now tried in the same repository to revert the Al-go for github version back to version 6.1, then the publish to enviroment actions works fine, but CI/CD fails because of the deprecated action in Git.

Expected behavior

Expected that the build will get deployed and not fail because of missing dependency to API V2, that is present in the enviroment.

Steps to reproduce

Create an App that is dependent on API V2 Microsoft app.
Run either CI/CD or Publish to environment.

Additional context (logs, screenshots, etc.)

[freddydk]

Sounds like the same problem as #1540

@spetersenms - any chance you could have a look at this?

[spetersenms]

I was not able to repro the issue, but it seems to me the issue is related to installation of the exclude app. I have a potential fix ready, but will need to test further Monday before I can deploy it.