v4.4.0: Sliding limit feature and revived Web support

I'm super happy to release the Slider with v4.4.0 which brings you two significant improvements:

• Sliding limit feature - authored by @alfonsocj in #432. This feature introduces two new properties: lowerLimit and upperLimit.
  These new props will prevent user from sliding below or above their values. This pull request also added the example cases of how to use these new props, so definitely check this PR for more details.
  Also thanks to @erikaannesmith for pushing this topic forward at some point.
• Revived Web support - authored by @jspizziri in #462. This implementation actually brings back the Web support of Slider, but also introduces the missing thumbImage support to the web implementation.
  This pull request also introduced the example-web/ which shows the state of web platform support of Slider.
  There were also several defects fixed within this one PR, and actually too many for me to list them here, so please spent a minute checking out this work.

I would like to say huge THANK YOU to @alfonsocj, @jspizziri and @erikaannesmith for their contribution to the Slider. 💪

---

As always, this release brings few internal chore improvements, so in case of any issues please do not hesitate to reach out to Issues section, or create a new issue in case of encountering anything new.

v4.3.3: Quality of Live improvements and bugfixes

This release brings some fixes and improvements to the Slider, including:

• fix(#249): regarding issue introduced in IOS 14 UISlider needs to force the layout (#450)
  @MateWW
• Replace dispatchModern() calls with getEventData() (#444)
  @notjosh
• Fix types being present as a prod dependency (#448)
  @liamjones
• Update the documentation for accessibilityIncrements (#441)
  @appfr3d

All of the listed fixes were made by new contributors so huge "Thank you!" to them for their contributions 👍

v4.3.2: Slider installation fail - fix

This release fixes the Slider installation previously failing due to README that could not be found (#430).
The fix:

• Fix: move postinstall script to prepack #433

was provided to you by @rborn

v4.3.1: New arch hotfixes

This release brings two hotfixes of issues introduced along with new architecture release:

• Configure buildscript only for new arch (#419)
• [Fabric] Fix hot reloading causing photo jumps (#413)

v4.3.0: React Native new architecture support

This version introduces the support of React Native new architecture.
This was implemented in #410 by @okwasniewski
It was a huge amount of decent work, so I strongly encourage to check out the PR and give the Slider a go with new architecture in your app.
To do that, upgrade Slider package in your app and follow the official guide on how to migrate your app to new architecture.

This update does also introduce some improvements/changes "under the hood" so in case of any problems/errors please report them by creating new issue.

v4.2.4: Bug fixes and minor chore improvements

• Fix: ignored step value during dragging (#393)
• Update docs regarding controlled value (#392)
• Removing hardcoded style attribute from the constructor causing resource not found error (#385)
  @KunalFarmah98
• fix: Change WindowsTargetPlatformVersion to 10.0 (#384)
  @namrog84

v4.2.3: Hotfix for Android default value

This release brings the hotfix for ignored default Android value issue.

• fix: do not reset the seekbar listener when setting the value (#387)

v4.2.2: Bugfixes and improvements

This release introduces several fixes and improvements, as well as some of the dependencies updates.

What has changed:

• Fix: SeekBar on Android is rendering incorrectly in RTL mode (#371)
  @pavel-stryber
• Fix: onChange is not called for tap when on Android (#367)
• Fix: onAccessibilityAction causes crash (#368)
• Fix: Type error when using Slider with props as ref (#369)

For full changelog please refer to: v4.2.1...v4.2.2

v4.2.1: Fix for conflicting disable states in accessibility

• Fix: Conflicting states for accessibility and non-accessibility users (#354)
  @fabriziobertoglio1987

v4.2.0: Controlled value

This release introduces the value property refactored so that it can be easily used to programmatically control the position of the thumb.

Most important notes about the updated value property:

• Can be used to programmatically control the position of the thumb,
• Affects the thumb's position immediately once updated
• Programmatic update to the value does not trigger the onValueChange event
• When updated during manual dragging the manual update has priority
• Property is still optional and can be still used as an initial value only

For more information please visit the PR implementing the feature: #349