Handle edge cases with NaN/Infinity

[lewisjkl]

When using a Query Parameter of type Double that has a Range constraint, NaN values will cause an exception to be thrown that would lead to a 500 error being returned by the service. The reason for this is that the Range RefinementProvider uses BigDecimal under the hood and BigDecimal does not allow NaN.

This PR updates the Range RefinementProvider to return an error that will map to a 4xx response. Additionally, the MetadataDecoder has been updated to allow configuring whether or not NaN should be allowed. AWS protocols allow NaN, whereas alloy#simpleRestJson does not.

Tests have been added to show that NaN is not currently supported by the json module or the Document type.

PR Checklist (not all items are relevant to all PRs)

• Added unit-tests (for runtime code)
• Added bootstrapped code + smoke tests (when the rendering logic is modified)
• Added build-plugins integration tests (when reflection loading is required at codegen-time)
• Added alloy compliance tests (when simpleRestJson protocol behaviour is expanded/updated)
• Updated dynamic module to match generated-code behaviour
• Added documentation
• Updated changelog

Will add relevant docs and update changelog once we know this is the direction we want to go.