Adding type any to the step parameter of EUIFIeldNumber

[shrey]

Summary

Provide a detailed summary of your PR. Explain how you arrived at your solution. If it includes changes to UI elements include a screenshot or gif.

Checklist

• Check against all themes for compatibility in both light and dark modes
• [] Checked in mobile
• Checked in IE11 and Firefox
• Props have proper autodocs
• Added documentation examples
• Added or updated jest tests
• Checked for breaking changes and labeled appropriately
• Checked for accessibility including keyboard-only and screenreader modes
• A changelog entry exists and is marked appropriately

@cchaos I don't know why changes from my old pr are showing up, but nw, as they're from the same PR that you merged Old PR
@chandlerprall
Related to issue:- #3550

[kibanamachine]

Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually?

[cchaos]

It's because you're using the same branch insteading starting again from the master branch. When we merge PR's we squash the commits into a single one. Github gets confused then and doesn't realize that your old commits were included in that single one. You'll need to fetch upstream, and start a new branch from master.