Specificity order for strings and bools in Encoder should swap when strictBooleans is enabled

[haltman-at]

Right now, strings are more specific than bools. If strictBooleans is on, this makes no sense; bools should be more specific. This is relevant because it could pose problems for overload resolution in Truffle Call, e.g. (Imagine if you wrote call C f true and got f(string) when you wanted f(bool)!)

Note that Encoder can't have specificity of types depend on the particular input, but there's no reason it can't have it depend on a flag like this. It should.

Environment

• Truffle version (truffle version): 5.8.4

[haltman-at]

Released in 5.9.4!