Introduce faster and richer way to add objects as query parameters

[ghost]

Description

This PR is a result of the discussion in PR#1897. It introduces a new way of adding objects as query parameters to a RestRequest instance when the object type is known beforehand, which allows for a lot of optimizations to be made.

Apart from this, this PR also builds on top of pre-existing functionality, allowing for things like:

• CSV and Array format is now available for all IEnumerable types.
• Formatting is applied to all formattable elements in an IEnumerable property.
• Properties are cached and getters are compiled into a delegate using LINQ Expressions for better performance.
• If a property is not IConvertible, IEnumerable or IFormattable, use the type's defined TypeConverter and delegate conversion to string to it instead of using .ToString(). This allows users to create custom converters to determine how certain types should be stringified. If no custom converter is defined, we will fall back to .ToString() anyways.
• Ref structs are properly ignored since they cannot be boxed and don't play well with reflection, which is not taken into account in the AddObject implementation.

Purpose

This pull request is a:

• Bugfix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist

• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)

[dnfadmin]

All CLA requirements met.

[alexeyzimarev]

Thanks for the PR. Please remember to sign the CLA.

[ghost]

Thanks for the PR. Please remember to sign the CLA.

Oops, my bad. Done. ✅

[ghost]

I'll look into what's happening with the test case that failed once I get home.

[ghost]

The test case that was failing was one that I had in place to ensure that ref structs are not taken into consideration when turning an object into query parameters, since they cannot be boxed and will throw at runtime, which is what happens with the default AddObject extension method.

I added a comment explaining the fix, but basically, I was filtering out properties based on whether they had a IsByRefLikeAttribute defined, but this attribute is generated by the compiler, and different assemblies will have different versions of this attribute, which was making this check useless. So now we're just checking if the property return type has any attributes with the full name "System.Runtime.CompilerServices.IsByRefLikeAttribute" instead.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[repo-ranger]

⚠️ This issue has been marked wontfix and will be closed in 3 days

[alexeyzimarev]

I had to merge it manually, for some reason GitHub doesn't recognise it.