Fix NPE in DoubleAttributeConverter and FloatAttributeConverter for null input

[S-Saranya1]

DoubleAttributeConverter.transformFrom() and FloatAttributeConverter.transformFrom() throw a NullPointerException when called with a null input due to auto-unboxing in ConverterUtils.validateDouble()/validateFloat(). This occurs when users persist a Map<String, Double> or List containing null values.

Motivation and Context

• Added null check in DoubleAttributeConverter.transformFrom() to return nullAttributeValue() for null input
• Added null check in FloatAttributeConverter.transformFrom() to return nullAttributeValue() for null input
• This follows the existing pattern used by StringAttributeConverter

Modifications

• Added null input assertions in NumberAttributeConvertersTest for both DoubleAttributeConverter and FloatAttributeConverter
• Existing tests continue to pass

Testing

Screenshots (if appropriate)

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)

Checklist

• I have read the CONTRIBUTING document
• Local run of mvn install succeeds
• My code follows the code style of this project
• My change requires a change to the Javadoc documentation
• I have updated the Javadoc documentation accordingly
• I have added tests to cover my changes
• All new and existing tests passed
• I have added a changelog entry. Adding a new entry must be accomplished by running the scripts/new-change script and following the instructions. Commit the new file created by the script in .changes/next-release with your changes.
• My change is to implement 1.11 parity feature and I have updated LaunchChangelog

License

• I confirm that this pull request can be released under the Apache 2 license

[sonarqubecloud]

Quality Gate passed

Issues
2 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud