fix: Support delimiters(_-.~) as start or end characters for a segment.

[blakeli0]

Support delimiters(_-.~) as start or end characters for a segment if the segment does not contain complex resource names.

• A segment can start with a delimiter, as long as there is no { right after it.
• A segment can end with a delimiter, as long as there is no } right before it.
• A segment like .{well}-{known} or {well}-{known}. is invalid.
• A segment like .well-known, .well-{known} or .-~{well-known} is considered a literal hence is valid

Fixes #335 ☕️

BEGIN_COMMIT_OVERRIDE
fix: Support delimiters(_-.~) as start or end characters for a segment
END_COMMIT_OVERRIDE

[vam-google]

LGTM, but please check the seg.length() > 1 check comment first

[blakeli0]

LGTM, but please check the seg.length() > 1 check comment first

Thanks, I see what you mean now, sorry I misunderstood you earlier. On the other hand, I think the way it is now might be better since it's cleaner and easier to read. Moving seg.length() > 1 would only benefit if the segment contains one character which I think is a very rare case.