feat: Add flexibility to get other props as a part of renderText function

[nikhil-varma]

Describe the issue/change

In the current system, we cannot get access to the custom props that are passed in the renderText method.

Add CodeSandbox link to illustrate the issue (If applicable)

Describe the changes proposed/implemented in this PR

This PR introduces another parameter in the renderText method in order to get the props passed to the component

Link Github issue if this PR solved an existing issue

Issue: #456

Example usage (If applicable)

 <NumberFormat
        displayType="text"
        className="foo"
        someRandomProps="someValue"
        value="123"
        renderText={(formattedValue, props) => {
          // Do something with obtained props
          return <span>{formattedValue}</span>;
        }}
      />

Screenshot (If applicable)

Please check which browsers were used for testing

• Chrome
• Chrome (Android)
• Safari (OSX)
• Safari (iOS)
• Firefox
• Firefox (Android)

[s-yadav]

@naman03malhotra @ParthS007, CI not working on PRs, can anyone take a look into this.

[ParthS007]

I can make PR. @naman03malhotra Please let me know if you have already started working on this.

[ParthS007]

@s-yadav I made the PR fixing the CI run. #486

After merging my PR, you have to change the required status for the CI with the new one.

[s-yadav]

@ParthS007, Merged your changes. The action seems working correctly now.

[nikhil-varma]

@s-yadav Ready for review 😄

[ParthS007]

@nikhil-varma Can you please rebase your branch with the latest master for CI to run. Thanks

[nikhil-varma]

@ParthS007 Done! 😄

[nikhil-varma]

@s-yadav Can you please verify if the changes are good to go! 😄

[s-yadav]

LGTM, can you add spec for the change.

[nikhil-varma]

@s-yadav Specs are added. Please review if it looks good! Thanks!

[nikhil-varma]

@s-yadav Should we go ahead and close the linked issue? Or wait until we release the new patch/version and then do it? What is the convention that we follow?

[s-yadav]

Will release a new version.
One thing we missed, we will have to update the readme to reflect this new param.

[nikhil-varma]

@s-yadav Right! I will update the readme and create a PR for this.