Entering data using Line Protocol from the UI has very poor error message when timestamp is older than retention policy

__Steps to reproduce:__
List the minimal actions needed to reproduce the behavior.

1. Create a bucket that has a retention policy that is not very long, i.e. not longer than 1 year
2. Select Load Data -> Line Protocol -> Enter Manually -> select bucket -> enter the example data (which has a timestamp from 2019
3. Click on Write Data

__Expected behavior:__
Should give a nice error message that says the data is too old for the retention policy. Or, at least the text that describes the process should remind the user that the timestamp must not be older than the retention policy allows.

__Actual behavior:__
Unable to Write Data ... unknown error

__Environment info:__

* System info: Run `uname -srm` and copy the output here: Linux 5.15.0-56-generic x86_64
*
* InfluxDB version: Run `influxd version` and copy the output here: InfluxDB v2.6.0 (git: 24a2b621ea) build_date: 2022-12-15T18:47:00Z
* Other relevant environment details: Container runtime, disk info, etc

Reproduce the issue through Load Data → Line Protocol → Enter Manually with a timestamp older than the selected bucket's retention policy. Trace the UI's “Unable to Write Data ... unknown error” path and make the completed behavior explain that the data is too old, then verify the manual-entry flow shows the useful message.

Written by the indexing model from the issue text.