Fix(Revit) : Use speckle newtonsoft instead of System.Text.Json for in dll conflict management project

[connorivy]

Description & motivation

Once Bilal upgraded to the connector version with dll conflict mangement, he was met with the conflict dialog option even though previosly he wasn't running into any conflicts.

Turns out that the only dependency introduced in the dll conflict manager, System.Text.Json, caused a new conflict. In this PR I replaced System.Text.Json with Speckle.Newtonsoft.

I also introduced a new way to exclude conflicts because bilal was getting a conflict between our version of RevitAPI.dll. Now we are ignoring a conflict if the conflicting dll is a Revit dll.

Changes:

To-do before merge:

Screenshots:

Validation of changes:

Checklist:

• My pull request follows the guidelines in the Contributing guide?
• My pull request does not duplicate any other open Pull Requests for the same update/change?
• My commits are related to the pull request and do not amend unrelated code or documentation.
• My code follows a similar style to existing code.
• I have added appropriate tests.
• I have updated or added relevant documentation.

References

[AlanRynne]

Ouch, that one did not take long.... #3273 (comment) 😅

[AlanRynne]

Changes look good 🙌🏼 We should have used our own Newtonsoft from the get go 😢

[connorivy]

@AlanRynne

First thing I said when Bilal showed me this was, "Well, Alan called it"