fix(android): ApplicationSettings not returning precise stored numbers - #10094

PR Checklist

• The PR title follows our guidelines: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/CONTRIBUTING.md#commit-messages.
• There is an issue for the bug/feature this PR is for. To avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it.
• You have signed the CLA.
• All existing tests are passing: https://github.com/NativeScript/NativeScript/blob/master/tools/notes/DevelopmentWorkflow.md#running-unit-tests-application.
• Tests for the changes are included - https://github.com/NativeScript/NativeScript/blob/master/tools/notes/WritingUnitTests.md.

What is the current behavior?

ApplicationSettings.getNumber does not return the precise value of a stored number. That is because setNumber uses SharedPreferences.putFloat inside and float is 32-bit.

To reproduce

ApplicationSettings.setNumber("timestamp", 1668478505);
console.log(ApplicationSettings.getNumber("timestamp")); // Returns 1668478464

What is the new behavior?

ApplicationSettings.setNumber will store the precise value and return it as double.

Issue: https://discord.com/channels/603595811204366337/828973479343947787/1041908934266589195