(googledrive) Add package parameter to skip application launch after installation

[brogers5]

Description

This changeset adds an additional install argument to googledrive's silent arguments, which will prevent Google Drive's installer from automatically starting Google Drive after install.

Motivation and Context

Fixes #190.

--skip_launch_new (as documented in this help article) will prevent Google Drive from automatically starting post-installation. IMO, this would be a better solution than the proposed idea of scripting a window closure post-install, as this behavior could be overridden without requiring a package parameter that modifies the install script's behavior.

How Has this Been Tested?

Environments

Dev

• OS Build: Windows 11 Pro v10.0.22621.0 (64-bit)
• PowerShell version: 7.3.3
• Chocolatey version: 1.3.1

Chocolatey Test Environment

• Vagrant Box Version: 3.0.0
• VM Provider: Virtualbox (although practically Hyper-V, since I manually converted the resulting virtual disk)
• OS Build: Windows Server 2019 Datacenter v10.0.17763.0 (64-bit)
• PowerShell version: 5.1.17763.3770
• Chocolatey version: 1.3.1

Steps

1. Created a test package of the current version that consumes the modified scripts (i.e. choco pack).
2. In my Chocolatey Test Environment instance, Installed the test package (i.e. choco install googledrive --source="'.'").
3. Confirmed the package installation succeeds without errors.
4. Confirmed Google Drive is NOT launched by the installer.

Screenshot (if appropriate, usually isn't needed):

N/A

Types of changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [x] Breaking change (fix or feature that would cause existing functionality to change)
• [ ] Migrated package (a package has been migrated from another repository)

Checklist:

• [x] My code follows the code style of this repository.
• [ ] My change requires a change to documentation (this usually means the notes in the description of a package).
• [ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
• [ ] I have updated the package description and it is less than 4000 characters.
• [x] All files are up to date with the latest Contributing Guidelines
• [x] The added/modified package passed install/uninstall in the chocolatey test environment.
• [x] The changes only affect a single package (not including meta package).

[AppVeyorBot]

:white_check_mark: Package verification completed without issues. PR is now pending human review

[mkevenaar]

@brogers5 What if the user wants to keep the existing functionality? I prefer not to change the existing functionality and add this as an optional parameter. Could you please change that?

[soredake]

What if the user wants to keep the existing functionality?

I am (as a user) think that silent install should be really silent, with no windows, but others might not agree.

[AppVeyorBot]

:white_check_mark: Package verification completed without issues. PR is now pending human review

[brogers5]

While I'm inclined to agree with @soredake's take on this, it seems avoiding a potentially breaking change for current package consumers takes priority.

I've added a /NoStart package parameter which should append this argument.