tool-path option -- "Session tool" (#8716)

* Change to escape string via XML

* tool-path option -- "Session tool"

From the beginning design, shim and packageInstaller take package location from constructor and don't have assumption anymore. From previous discussion, tool-path will simply change global location to the one user want, and everything else is the same.

However, this "override" need to happen during the call, that means InstallToolCommand will create different shim and packageInstaller object according to the tool-path during the call instead of constructor DI.

* global package location change

* block of leading dot as command name

* Localization of tool-path option

src/dotnet/xlf/CommonLocalizableStrings.es.xlf

@@ -858,6 +858,11 @@ setx PATH "%PATH%;{0}"
         <target state="new">Failed to find staged tool package '{0}'.</target>
         <note />
       </trans-unit>
+      <trans-unit id="ToolSettingsInvalidLeadingDotCommandName">
+        <source>Command '{0}' has a leading dot.</source>
+        <target state="new">Command '{0}' has a leading dot.</target>
+        <note />
+      </trans-unit>
     </body>
   </file>
 </xliff>