Suggested Change of UAL Dump Format from json to jsonl

[0x534a]

🗣 Description

In this PR, we suggest to change the output format of the Microsoft 365 UAL dump from JSON to JSON lines.

💭 Motivation and context

All of the output files of the Microsoft 365 dumper module are in JSON line format except the UAL which is written as a single JSON object. In order to be more consistent and to improve the performance of parsing the dumped UAL, we suggest to change the output format from a single JSON object to the JSON line format.

🧪 Testing

This PR was tested manually against a Microsoft 365 development tenant (E5 license).

✅ Pre-approval checklist

• [x] This PR has an informative and human-readable title.
• [x] Changes are limited to a single goal - eschew scope creep!
• [x] All future TODOs are captured in issues, which are referenced in code comments.
• [ ] All relevant type-of-change labels have been added.
• [x] I have read the CONTRIBUTING document.
• [ ] These code changes follow cisagov code standards.
• [ ] All relevant repo and/or project documentation has been updated to reflect the changes in this PR.
• [ ] Tests have been added and/or modified to cover the changes in this PR.
• [ ] All new and existing tests pass.

✅ Pre-merge checklist

• [ ] Revert dependencies to default branches.
• [ ] Finalize version.

✅ Post-merge checklist

• [ ] Create a release.

[victoriawallace-cisa]

We're currently testing this PR.

[victoriawallace-cisa]

Hello, we've merged the PR into the tool, but we did not notice any file format or run time differences between the two. We guess it's because the UAL is dumped as a single object so there's no big difference in the json or jsonlines format.