Pull To Refresh - Phase II

[MartinZikmund]

GitHub Issue (If applicable): closes #

PR Type

What kind of change does this PR introduce?

• Feature

What is the current behavior?

• IRefreshInfoProvider not used and not supported
• RefreshVisualizer cannot be customized

What is the new behavior?

• IRefreshInfoProvider is supported and used as a native implementation bridge
• RefreshVisualizer can be customized on iOS

PR Checklist

Please check if your PR fulfills the following requirements:

• [ ] Docs have been added/updated which fit documentation template (for bug fixes / features)
• [ ] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
• [ ] Validated PR Screenshots Compare Test Run results.
• [ ] Contains NO breaking changes
• [ ] Associated with an issue (GitHub or internal) and uses the automatic close keywords.
• [ ] Commits must be following the Conventional Commits specification.

Other information

Internal Issue (If applicable):

[gitpod-io[bot]]

[MartinZikmund]

@jeromelaban Definitely can try to add one in the next phase (will be adding the custom visualizer support anyway), but for now I would prefer to merge as is.