What happened?
Monkey365 fails to scan when Purview service is selected.

How to reproduce it
Steps to reproduce the behavior:

1. Execute the following command:

Invoke-Monkey365 -Instance Microsoft365 -Collect Purview -ExportTo CSV -Verbose -Debug -InformationAction Continue

2. See error

Expected behavior
Execute Monkey365 against Purview instance with no exceptions

Additional context
Monkey365 relies on collector's folder name when searching for valid collectors, which can return incomplete results when the folder is renamed. Some folders were renamed to comply with new brand names (e.g. Security & Compliance folder was renamed to Purview).

Note That issue is partially fixed on dev branch, but the search logic must be updated