[Work Item] SetupAssist additional logic to find Schema issues

[johage]

Describe the work
When running PrepareSchema we can check the ExchangeSetupLogs to confirm the failure and then reference LDIF.ERR and LDIF.LOG in the user path. (C:\users\NAME\AppData\Local\Temp). Example of the error for one such scenario:
Add error on entry starting on line 355: Unwilling To Perform
The server side error is: 0x20bb Schema update failed: duplicate OID.
The extended server error is:
000020BB: SvcErr: DSID-0326036D, problem 5003 (WILL_NOT_PERFORM), data 8379

Additional Context
In the ExchangeSetupLogs we'll point to the LDF files that'll be present in the mounted ISO path under Setup\Data\ like so:
"C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf"

We'll then also call out the User path like so:
[ERROR] There was an error while running 'ldifde.exe' to import the schema file 'C:\Windows\Temp\ExchangeSetup\Setup\Data\PostWindows2003_schema0.ldf'. The error code is: 8245. More details can be found in the error file:

We have static AttributeIDs that are referenced as the OID in the logging. These can be captured by Get-ADObject where we'd then be able to match up against AttributeID with something like this:
Get-ADObject -Filter 'Name -like "*"' -SearchBase "CN=Schema,CN=Configuration,DC=DOMAIN,DC=com" -Properties AtrributeID