Implement MAC address support

[mkgrgis]

This PR implements PostgreSQL macaddr and macaddr8 columns support as possible mixed affinity column in SQLite. The nearest affinity selected as integer because of there are many fast operations in SQLite including | and &.
After this PR sqlite_fdw will can deal with both 12-34-56-78-9A-BC text , 0x0123456789ABC integer and X'0123456789ABC' blob notations.
In this PR also:

• all data type tests moved to subdirectory types instead of extra because of tests of different data types are majority of tests in extra subdirectory.
• sed from test.sh changed to environment variable REGRESS to deal with partial or non-default tests. This allows define REGRESS and do not touch Makefile content. In case of void REGRESS variable default list of tests is applied.

[mkgrgis]

@t-kataym, could you please plan review of this ready PR by pgspider team?

[son-phamngoc]

@mkgrgis Thank you very much for your hard work.
I have some comment for this PR. Please help me to check them.

[mkgrgis]

All your comments have been checked, @son-phamngoc ! Please ensure now this PR is normal. I'll squash all commits if all is good before merging.

[mkgrgis]

@son-phamngoc, look like all of the problems are resolved. Please confirm current implementation and start 3rd round of review.

[son-phamngoc]

@mkgrgis Please check 2 comments #101 (comment) and #101 (comment). I think this PR will be OK for my review after you fixed them.

[mkgrgis]

Thanks, @son-phamngoc ! All problems are fixed. This PR is ready for squashing and review by @t-kataym .

[mkgrgis]

@son-phamngoc , FYI rebased and merged branch macaddr + PostGIS was successfully tested.

[mkgrgis]

@son-phamngoc , could you please explain current status of this PR? Is it planned for merging after PostGIS PR?

[t-kataym]

@mkgrgis We are in progress to release new version for supporting PostgreSQL 17. Could you wait for that and then rebase this PR? Then I would like to merge it.

[mkgrgis]

No problems, @t-kataym ! Like most for other my PRs here are no many changes expected.

[mkgrgis]

Could you wait for that and then rebase this PR?

@t-kataym , why not inverse order? How do you think, is PostgreSQL 17 support patch for this PR simpler than rebase patch for this PR after PostgreSQL 17 support?

[t-kataym]

@mkgrgis I'm sorry for the inconvenience. It comes from an internal process for release in our company. I appreciate your understanding.

[mkgrgis]

Thanks for clarification, @t-kataym ! I have understood there is private draft branches which have priority for merging during release process.

[t-kataym]

@mkgrgis Thank you for your understanding and waiting for it.
I have modified the code to support PostgreSQL 17(#106).
Could you rebase this PR?

[mkgrgis]

@t-kataym, rebasing is complete. Please review current result or/and discuss previous results of the PR with @son-phamngoc.

[t-kataym]

@mkgrgis Thank you for your effort.
@son-phamngoc Could you confirm it again?

[son-phamngoc]

@mkgrgis Thanks for your hard work.
I have some comments. Please help me to check them.

[mkgrgis]

@son-phamngoc , look like all problems are resolved. I am ready to merge this PR to GIS branch if this PR will be merged to pgspider's master.

[son-phamngoc]

@mkgrgis Thanks for your contribution. I have no more comment.
Please wait for @t-kataym's decision.

[mkgrgis]

Thanks for review, @son-phamngoc !

[t-kataym]

@mkgrgis Thank you for your effort.
@son-phamngoc Thank you for your confirmation.
I will merge the PR.