feature: adding support for lseg type

[avinash-anand]

Make sure that:

• You have read the contribution guidelines.
• You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
• You use the code formatters provided here and have them applied to your changes. Don't submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.

Issue description

related to issue previously opened support for geometric types - #282

New Public APIs

Additional context

[avinash-anand]

@mp911de - please review and let me know if something needs improvement.

[mp911de]

Thanks a lot. We received a pull request that brings support for all remaining geo types, see #306. Since the other pull request duplicates this one and completes the geo type story, I'm inclined to close this one in favor of #306. What do you think?

[avinash-anand]

Thanks a lot. We received a pull request that brings support for all remaining geo types, see #306. Since the other pull request duplicates this one and completes the geo type story, I'm inclined to close this one in favor of #306. What do you think?

@mp911de - sure. I can close this PR.
I have another question - Can I open separate issue for support for postgis plugin data types? Is this repo good place for those data type codecs?

[mp911de]

Thanks a for your feedback. Postgis for JDBC is part of an external library. I'd advise to follow the same design for R2DBC. With CodecRegistry in place, any external library can provide an extension through Java's ServiceLoader mechanism so that the driver is going to pick it up. Reaching out to the maintainers of https://github.com/postgis/postgis-java would be a good idea to keep all Postgis code in a single place.