ICU-23345 Require Range to be a range in UTFStringCodePoints to improve error messages

[eggrobin]

Suggested by @jmr after seeing the error messages generated by UTFStringCodePoints<..., char> (which was how this API worked in an earlier draft).

TODO: Fill out the checklist below.

Checklist

• Required: Issue filed: ICU-23345
• Required: The PR title must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
• Required: Each commit message must be prefixed with a JIRA Issue number. Example: "ICU-1234 Fix xyz"
• Issue accepted (done by Technical Committee after discussion)
• Tests included, if applicable
• API docs and/or User Guide docs changed or added, if applicable

[eggrobin]

@markusicu, should this target main on a new ticket, or 78 maintenance on a reopened ICU-23004?

[markusicu]

@markusicu, should this target main on a new ticket, or 78 maintenance on a reopened ICU-23004?

@eggrobin is this PR fixing problems, or just "improv[ing] error messages"?
If it's an important bug fix, then it should go onto the maintenance branch, with the existing ticket.
If it's merely an improvement, then it should go onto main for ICU 79.

@mihnita @richgillam FYI

[markusicu]

lgtm as an improvement for ICU 79 -- please create an ICU 79 ticket for such improvements

[markusicu]

please create an ICU 79 ticket for this

[richgillam]

This LGTM, but it involves newer C++ idioms that I'm not familiar with, so take everything I say with a grain of salt.

[markusicu]

Is it possible to write a meaningful unit test for this?

[eggrobin]

Is it possible to write a meaningful unit test for this?

If it doesn’t change the API, not within the language.

It might be useful to set up a test harness that puts expectations on error messages, but not today.

[jira-pull-request-webhook]

Hooray! The files in the branch are the same across the force-push. 😃

~ Your Friendly Jira-GitHub PR Checker Bot

[markusicu]

FYI: CI checks finished & passed (and I approved last week)