Refactor custom components to be render functions

[IB3N]

Reasons for changes

• Adding custom components by just passing a component as a prop (like customCloseComponent) is almost useless because then the only way to close the story is by swiping down from the top
• This way uses a system such like react-native-tab-view's renderTabBar function
• This allows passing the current item and onPress or profileName as props to the render functions so they can have access to the onClosePress function
• This is useful in situations where you want to add another button component next to the close/swipe button which has it's own onPress prop. For example adding a share story button next to the close button like so:
• adding customProps to the IUserStoryItem enables users to add their own props, which is then useful for rendering a custom text component, for example, say adding the age of a instagram story which can be rendered underneath the users profile name (like instagram)

Summary of changes

• [x] add:
  • renderSwipeUpComponent
  • renderCloseComponent
  • renderTextComponent
• [x] add IUserStoryItem.customProps

Important ⚠️

• This is a breaking change and should incur a major release versioning update

[IB3N]

@caglardurmus please let me know if you would like this not to be a breaking change - I can add the previous props back in and account for them and throw some developer errors if both props are passed, or create something like a CSS cascading order of priority.

Cascading example: oldProp > new renderProp -> defaultPackageComponent

[lucasdzuc]

@IB3N Are these changes already added?

[IB3N]

@lucasdzuc I don't think so, this is the PR to merge them right?