feat(manager/azure-pipelines): Add Azure DevOps project support

[robjackstewart]

Changes

• Add support for bumping Azure Pipeline template dependencies across different Azure DevOps projects by making the current repository accessible as part of the ExtractConfig interface.
• Add logic to determine the target Azure DevOps when looking for dependency updates.

Context

When an azure pipeline template declares an Azure Repos repository resource, the name of the repository may be prefixed with the Azure DevOps project name e.g. repo: Project/Repository. However, the project name is not mandatory and omitting it makes the reference to the current project implicit.

For example:
If a repository called MyRepository is in Azure DevOps project MyProject, and there is an Azure Pipelines YAML file which declares a repository resource as repo: MyOtherRepository, then Azure Pipelines assumes that MyOtherRepository is in project MyProject. Whereas if MyOtherRepository was in a different project it would need to be declared as repo: MyOtherProject/MyOtherRepository.

Renovate cannot currently update dependencies if the project is implicit because we do not pass in context about the repository being processed to the manager.

Supporting discussion.

Documentation (please check one with an [x])

• I have updated the documentation, or
• No documentation update is required

How I've tested my work (please select one)

I have verified these changes via:

• Code inspection only, or
• Newly added/modified unit tests, or
• No unit tests but ran on a real repository, or
• Both unit tests + ran on a real repository

[CLAassistant]

All committers have signed the CLA.

[robjackstewart]

Ah damn! I'll fix up those unit tests.

[viceice]

needs test updates

[robjackstewart]

needs test updates

Tests show now be fixed.

[renovate-release]

🎉 This PR is included in version 37.235.0 🎉

The release is available on:

• GitHub release
• npm package (@latest dist-tag)
• 37.235.0

Your semantic-release bot 📦🚀