FeaturePanel: Arrow for direction tag

[Dlurak]

Description

Add a arrow for the direction tag. This fixes #590

### examples:

• https://osmapp.org/cDS6hn
• https://osmapp.org/node/3301917161 (value -15 broken)

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
osmapp	✅ Ready (Inspect)	Visit Preview	Sep 24, 2024 3:29pm

[sentry-io]

🔍 Existing Issues For Review

Your pull request is modifying functions with the following pre-existing issues:

📄 File: src/components/FeaturePanel/Properties/renderValue.tsx

Function	Unhandled Issue
renderValue	TypeError: t is undefined /[[...all]] Event Count: 97 Affected Users: 6
renderValue	TypeError: undefined is not an object (evaluating 't.match') ... Event Count: 84 Affected Users: 4
renderValue	TypeError: Cannot read properties of undefined (reading 'match') ... Event Count: 11 Affected Users: 1
renderValue	TypeError: Cannot read properties of undefined (reading 'replace') ... Event Count: 10 Affected Users: 1
renderValue	TypeError: undefined is not an object (evaluating 't.replace') ... Event Count: 3 Affected Users: 1

---

_{Did you find this useful? React with a 👍 or 👎}

[zbycz]

I would suggest returning a null here, because value in OSM can be very creative. Let's don't stop entire application, but just hide the direction indicator.

In general - exceptions are meant for app states we really don't expect. User input usually shouldn't throw an exception.

[Dlurak]

Often there are directions that aren't cardinal e.g. on road signs backward and forward is used.
This will throw here and will be catched in DirectionValue a few lines lower.
In my opinion this is the easiest way to cancel the arrow rendering.

[zbycz]

Please, can you add examples of features with direction in the PR description? also with the range? thx.