Should Equivalency compare Enums by string or value?

Hi,
My use case is to verify automapper mapping results.
I have 2 equivalent enums defined in my contract and in my DTO, but FluentAssertion fails to see the their values as equivalent, because they are not the same type.

I can easily `ExcludeMissingProperties` which helps a lot. then I only miss a way to compare enums for a super simple an generic way to test Automapper mappings.

If that is something that we want, I would suggest an option to treat enums by value or by string.
I looked at the code, I would gladly implement it this weekend :)

    options.CompareEnumValues();

or

    options.CompareEnumToString()

What do you think?
In general the equivalency API doesn't care too much about a property's type, so I would drop the original comparison method and make `CompareUnderlyingValues` the default behavior.