AVD CIT Script for Installing FSLogix sets CCDLocations erroneously

The Profile Path option in FSLogix needs to be expanded upon to include options for not using CloudCache

CCDLocations is only used for CloudCache whereas VHDLocations is used for Profile Folders. There is a bug where having CCDLocations and VHDLocations set at the same time will cause FSLogix to hang on logout.

Per https://learn.microsoft.com/en-us/fslogix/concepts-configuration-examples you will never see both VHDLocations and CCDLocations used at the same time. CCDLocations is only relevant (assuming you choose to use CloudCache) if you have at least 2 distinct storage locations within the same region for your profile containers.

This means the configuration item should be expanded out to allow choosing to enable CloudCache or not, and if CloudCache is enabled, then Profile Path will set CCDLocations and must contain at least 2 distinct providers. Otherwise VHDLocations is set and by best practice should only have 1 provider set.

Additionally, for those organizations who plan to use Group Policy or Intune to set their FSLogix settings, there should be an option to install the latest FSLogix build but _not_ actually perform any configuration settings.

Locate the AVD CIT PowerShell script and its Profile Path configuration handling. Read how it currently assigns CCDLocations and VHDLocations, then trace the installation path. Done means CloudCache can be explicitly enabled or disabled with the corresponding location rules, and installation can skip configuration for Group Policy or Intune-managed deployments.

Written by the indexing model from the issue text.