issue 112 fixes (rework how long JSON paths are managed)

[ztrhgf]

Solution to #112 (comment)

Instead of using the resource item scope as a JSON file name (with some modifications), split the path into smaller chunks (represented as directory names now), and do the same for JSON file name itself.

This way, the risk of having a file with a too-long name is minimized.

[ztrhgf]

3.0.1

            FIXED
            - path processing on linux
            - sort issues on linux machines (replaced "sort" with "Sort-Object")

            CHANGED
            - sort JSONs properties before export to avoid clutter in git history when just order of the object properties was changed
            - optimized batch request processing by running multiple batch requests in parallel (PowerShell Core only!)
            - added ThrottleLimit parameter to Export-Entra to control the number of concurrent batch requests (PowerShell Core only)
            - RAM optimization: one schema item (and children) processed at once. Instead of all parent schema (and all children items) items at once.
            - IAM and AccessPolicies export: creating directory structure to mimic the scope (to minimize long path issues)
            - reworked how PIM assignments for Resources are being exported to avoid long path issues