Distribution.Client.ProjectBuilding.PackageFileMonitor

As part of the dry run for local unpacked packages we have to check if the package config or files have changed. That is the purpose of PackageFileMonitor and checkPackageFileMonitorChanged.

When a package is (re)built, the monitor must be updated to reflect the new state of the package. Because we sometimes build without reconfiguring the state updates are split into two, one for package config changes and one for other changes. This is the purpose of updatePackageConfigFileMonitor and updatePackageBuildFileMonitor.

This is all the components of the BuildResult other than the [InstalledPackageInfo].

We have to split up the BuildResult components since they get produced at different times (or rather, when different things change).

Helper function for checkPackageFileMonitorChanged, updatePackageConfigFileMonitor and updatePackageBuildFileMonitor.

It selects the info from a ElaboratedConfiguredPackage that are used by the FileMonitors (in the PackageFileMonitor) to detect value changes.

Do all the checks on whether a package has changed and thus needs either rebuilding or reconfiguring and rebuilding.