(#3315) Save software installation location

[TheCakeIsNaOH]

Description Of Changes

Saves the location of where the contents of the Chocolatey package
(whether that is a native installer, or an extraction of a zip file, or
whatever else is in the package) is deployed to into a
".deploymentLocation" file inside the package info directory.

This allows Chocolatey CLI or GUI to later retrieve it and display it to
the user when listing the details of locally installed package(s).

Motivation and Context

See #3315

Testing

1. .\choco.exe install wget --force
2. Ensure that the software location is logged and a .softwareLocation file containing the path is created in the folder under .chocolatey
3. .\choco.exe install wget --skip-powershell --force
4. Ensure that there is no software location logged and there is no .softwareLocation file
5. .\choco.exe install balcon
6. Ensure that the software location is logged and a .softwareLocation file containing the path is created in the folder under .chocolatey

Operating Systems Testing

• Windows 10 22H2

Change Types Made

• Bug fix (non-breaking change).
• Feature / Enhancement (non-breaking change).
• Breaking change (fix or feature that could cause existing functionality to change).
• Documentation changes.
• PowerShell code changes.

Change Checklist

• Requires a change to the documentation.
• Documentation has been updated.
• Tests to cover my changes, have been added.
• All new and existing tests passed?
• PowerShell code changes: PowerShell v2 compatibility checked?

Related Issue

Fixes #3315

[gep13]

@TheCakeIsNaOH based on a conversation with @pauby I have taken the liberty of making some changes to this PR.

We are going to move forward with the concept of things being "deployed", since a Chocolatey package can have more than just software in it. So things like .softwareLocation and are changed to .deploymentLocation.

[gep13]

The testing steps are not quite right on this PR, but the concepts are still valid.

For example, even with the skip-powershell option, a .deploymentLocation file is still created, however, it points to the package folder, rather than the tools folder within the package.

This is the correct action, and I think that this was a change in output since the PR was created.

[gep13]

LGTM!

[gep13]

@TheCakeIsNaOH thank you (again) for all your work here!