Better exception messages for breps that fail to meshify

[JR-Morgan]

CreateFromBrep will return null if a brep fails to meshify with the provided meshing options.
I notice that this with minimumEdgeLengh in particular on some breps.

In v2, we exposed these tolerances as options. But in leu of that, this PR just gives a clearer exception message

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 2 lines in your changes missing coverage. Please review.

Project coverage is 8.71%. Comparing base (ddd6039) to head (eb8580a).

Files with missing lines	Patch %	Lines
...noShared/ToSpeckle/Meshing/DisplayMeshExtractor.cs	0.00%	2 Missing ⚠️

Additional details and impacted files

@@           Coverage Diff            @@
##             dev    #634      +/-   ##
========================================
- Coverage   8.71%   8.71%   -0.01%     
========================================
  Files        227     227              
  Lines       4370    4372       +2     
  Branches     545     546       +1     
========================================
  Hits         381     381              
- Misses      3974    3976       +2     
  Partials      15      15              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[clairekuang]

The append method will also throw if any of the meshes inside render meshes is null, not just the list itself:

In v2, we were trycatching this operation. Can do the same and rethrow the exception

[JR-Morgan]

I'm not attempting to make it impossible for this function to throw an ArgumentNullException, I simply want to handle the expected case where Rhino's API returns an empty Mesh[] when a BREP can't be meshified.

In my testing, I did not see any cases where it returns an array with null values inside of it.
So if that happens, it would actually quite like for it to throw something dangerous that we can notice and raise our eyebrows at.