Calling 'C:\AL\AzureLabSources.ps1' if path on lab sources cannot be found

[raandree]

Description

Sometimes, files on the Azure LabSources share cannot be found. Calling the file C:\AL\AzureLabSources.ps1 fixes that. This workaround should be going to AutomatedLab and not to AutomatedLab.Common, however, calling C:\AL\AzureLabSources.ps1 may be required also when running in a scheduled task. This is why this workaround needs to go into this module.

• [x] - I have tested my changes.
• [x] - I have updated CHANGELOG.md and added my change to the Unreleased section
• [x] - The PR has a meaningful title.
• [x] - I updated my fork/branch and have integrated all changes from AutomatedLab.common/develop before creating the PR.

Type of change

• [x] Bug fix
• [ ] New functionality
• [ ] Breaking change
• [ ] Documentation

How was the change tested?

Exchange 2019 deployment

[raandree]

@nyanhp, I know that this breaks a rule (see #123) but as the function Install-SoftwarePackage sometimes runs as a schedule job on the lab machine. This AutomatedLab specific behavior is only triggered if the path to install starts with automatedlab*.

Sometimes, the Azure LabSources share is not connected. Calling the script C:\AL\AzureLabSources.ps1 solves the issue. I have also modified the script so it returns data about the status of the Azure LabSources share connection.