[FEATURE] test BU for missing system-folders

[JoernBerkefeld]

if these folders were not created properly during BU provisioning (something done in the background when one creates a new business unit) then this breaks all API operations around folders and hence brings mcdev to its knees.

2 implementations:

1. auto-run as part of preDeplpoymentTasks or during folder caching? If a parent folder is missing in cache and that folder happens to be in below list, bring deployment to full stop and present a readable error. Something along the lines of "pls contact sfmc support to correct folder xyz or create a new BU because something went wrong during BU provisioning of folder xyz"
2. offer new CLI command to quickly check a BU for missing folders. I am thinking of checkBU, which leaves room for future additional checks.

Relevant folders:

[
    "A/B Testing",
    "Auto-Suppression Configuration",
    "Content Builder",
    "Data Extensions",
    "Data Filters",
    "Filter",
    "HiddenCategory",
    "HiddenCategory/SystemHiddenPortfolio",
    "HiddenCategory/SystemHiddenPortfolio/SystemHiddenPortfolioForCC",
    "HiddenCategory/SystemHiddenEmails",
    "Journey Builder Sends",
    "Measures",
    "my automations",
    "my contents",
    "my documents",
    "my emails",
    "my groups",
    "my images",
    "my images/Forward to a Friend",
    "my journeys",
    "my lists",
    "my subscribers",
    "my surveys",
    "my templates",
    "my tracking",
    "my tracking/Salesforce Mass Sends",
    "my tracking/Salesforce Single Sends",
    "my workflows",
    "Portfolio",
    "Portfolio/Forward to a Friend",
    "Portfolio/Social",
    "Publication Lists",
    "Query",
    "Salesforce Data Extensions",
    "Salesforce Sends",
    "Scripts",
    "simple automated emails",
    "Suppression Lists",
    "Triggered Sends",
    "User-Initiated"
]

TBC with @DougMidgley