Range: Fix undefined pinFormatter on initialization

Which issue does this PR close?

This PR closes #3366

We always define a pinFormatter so we avoid initialization issues where the pinFormatter is undefined when forwarded to ion-range

The following tasks should be carried out in sequence in order to follow the process of contributing correctly.

[x] Make sure you have implemented tests following the guidelines in: "The good: Test".
[x] Make sure you have updated the cookbook with examples and showcases (for bug fixes, enhancements & new components).

[x] Determine if your changes are a fix, feature or breaking-change, and add the matching label to your PR. If it is tooling, dependency updates or similar, add ignore-for-release.
[x] Do a self-review.
[x] Request that the changes are code-reviewed
[ ] ~~Request that the changes are UX reviewed (only necessary if your PR introduces visual changes)~~

When the pull request has been approved it will be merged to develop by Team Kirby.