Breaking change in referenced DACPAC fails the deployment script creation about ssdtlifecycleextension

[Herdo]

The reason for this bug is that the DacPackage instances are loaded from a FileStream.
When the packages are loaded from any Stream, referenced DACPACs will be searched by an absolute path. This results in both the old DACPAC - which referenced the now missing column - and the new DACPAC - without the missing column - to reference the same shared DACPAC.
One expects the column, the other doesn't. This causes the error message shown the bug report.

To solve the issue, all calls to DacPackage.Load have to be changed from the Steam overload to the string overload.

In that case, when resolving references during the script generation, DacFX will use relative paths, e.g. look for the referenced DACPAC in the same directory as the DACPAC to create the script for.
This way, the old DACPAC will use the old shared DACPAC with the now missing column still there, while the new DACPAC will use the new shared DACPAC where the column is missing.

With this, it's not possible to use any Streams in tests. Therefore, tests for DacAccess should be scrapped.