Fix exception constructor argument order

[glopesdev]

For some reason the order of arguments into the ArgumentOutOfRangeException constructor was swapped in all instances of the call in the DirectedGraph class, most likely because it is the reverse order from the more common ArgumentException.

[PathogenDavid]

Good as-is, but it might be a good idea to swap most of these over to the ArgumentOutOfRngeException(string paramName) overload instead since their messages don't really add anything over the default one. (That overload is why the order is swapped from the base ArgumentException.)

---

It also might be worth enabling CA2208 to avoid this mistake in the future:

# Add to .editorconfig
dotnet_diagnostic.CA2208.severity = warning

Although it's worth noting that'll complain about inappropriate usage of ArgumentOutOfRangeException in Slice.cs. (Because they're locals rather than parameters, but I think it makes reasonable sense in a Bonsai context--could just suppress.)

[glopesdev]

Although it's worth noting that'll complain about inappropriate usage of ArgumentOutOfRangeException in Slice.cs. (Because they're locals rather than parameters, but I think it makes reasonable sense in a Bonsai context--could just suppress.)

Actually that was indeed another inappropriate use, so I've turned diagnostic severity to warning. We have been using InvalidOperationException rather than ArgumentException for these, but Slice is old enough that it retained some legacy.