DevCheck: Settings options, configuration dependency paths, Sync'd dependencies

[DrusTheAxe]

New options

• -Settings => Load the settings file (if exists) to enable future customization (default=$True)
• -SettingsFile=file => Settings file to load (default = ...repo....user\DevCheck-Settings.ps1)
• -SaveSettingsFile=file => Save a default settings file (fail if exists; won't overwrite existing files)
• -UserSettings => Load the user settings file (if exists) to enable future customization (default=$True)
• -UserSettingsFile=file => User Settings file to load (default = ...repo....user\DevCheck-Settings.ps1)
• -SaveUserSettingsFile=file => Save a default user settings file (fail if exists; won't overwrite existing files)

Settings file is for a project to customize behavior. User Settings file is per user to mess with.

NOTE: A future update will change the default location for Settings file (pending a change to DevCheck.cmd @kythant is working on)

Change -CheckDependencies and -SyncDependencies to use a customization list of root directories. Use a settings file with custom values for $global:dependency_paths e.g.

$global:dependency_paths = ('fee', 'fie', 'foe\fum')

Also ran -SyncDependencies to correct a couple of stale entries (FrameworkUdk from May(!))

[DrusTheAxe]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[DrusTheAxe]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).