Feature/139 add user deploy support - fixes

[JoernBerkefeld]

PR details

What changes did you make? (Give an overview)

• added "(Key: ...)" info after "Downloaded: x" for SOAP retrieves (so far this was only happening for REST retrieves)
• made "Requesting next batch..." gray given its lesser importance
• fixes [FEATURE] add user deploy support #139
  • allowed @ in filenames
  • renamed xxx__c fields to c__xxx to match the mcdev standard
  • removed c__AssociatedBusinessUnits from deploy payload
  • fix BU listing in document user's md file
  • add option to unlock users (those with IsLocked=true) by setting Unlock=true
  • the initial release was only tested on our internal server where it worked great
  • testing it on a client server with 90+ BUs and 2700+ users / installed packages some of the SFMC APIs broke down:
    • AccountUserAccount (BU assignments) only returned 20-25 BUs per user, even if 90 were assigned when trying to retrieve all without filter. Adding a filter with all AccountUserIDs had the same result --> Working through it 100 users at a time worked though.
    • AccountUser worked fine for the first 2500 returned records but on the 2nd page it would not return Roles nor UserPermissions anymore. --> decided to split the request into active users, inactive users, installed packages

Retrieve all:

Retrieve by key:

Deploy single user:

Deploy blocked due to Marketing Cloud role:

Checklist

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• test scripts updated
• Wiki updated --> unlock, marketing cloud roles --> via [TASK] update documentation for 5.0.0 release #722