Wrong error type in case of invalid amount in Interval components

[DDtKey]

Describe the bug
Currently, if Interval value contains invalid amount component NotYetImplemented error type is returned.
That doesn't seem correct, because such values are not going to be supported (or at least, it's confusing)

Let's take a look at such example:

INTERVAL '1 MONTH DAY'

This is an obvious typo/mistake which leads to such error, but in fact it's just invalid value (missing number before DAY)

To Reproduce
There are tests for this case already:

arrow-rs/arrow-cast/src/cast/mod.rs

Lines 4403 to 4417 in bb1250c

	test_unsafe_string_to_interval_err!(
	vec![Some("foobar")],
	IntervalUnit::YearMonth,
	r#"Not yet implemented: Unsupported Interval Expression with value "foobar""#
	);
	test_unsafe_string_to_interval_err!(
	vec![Some("foobar")],
	IntervalUnit::DayTime,
	r#"Not yet implemented: Unsupported Interval Expression with value "foobar""#
	);
	test_unsafe_string_to_interval_err!(
	vec![Some("foobar")],
	IntervalUnit::MonthDayNano,
	r#"Not yet implemented: Unsupported Interval Expression with value "foobar""#
	);

Expected behavior
Return ParseError, like other errors from parse_interval_components

Additional context

[alamb]

label_issue.py automatically added labels {'arrow'} from #5987