THRIFT-5575: add a github workflow to invoke cmake

[jimexist]

see also:

• THRIFT-5564: setup java and kotlin lib building #2593
• THRIFT-5564: setup rust building in GitHub action #2594
• THRIFT-5564: setup compiler-building github action [skip ci] #2592

• Did you create an Apache Jira ticket? (not required for trivial changes)
• If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
• Did you squash your changes to a single commit? (not required, but preferred)
• Did you do your best to avoid breaking changes? If one was needed, did you label the Jira ticket with "Breaking-Change"?
• If your change does not involve any code, include [skip ci] anywhere in the commit message to free up build resources.

[emmenlau]

Hi @jimexist ! I just wanted to point out that we have a work-in-progress PR for dotnet support in cmake. Its not really using the dotnet-capabilities of cmake, but rather cmake is creating build instructions that under the hood will call dotnet for the build. That's quite in line with what automake was doing, just from cmake. I can update my PR and push it again if you want me to?

[jimexist]

Hi @jimexist ! I just wanted to point out that we have a work-in-progress PR for dotnet support in cmake. Its not really using the dotnet-capabilities of cmake, but rather cmake is creating build instructions that under the hood will call dotnet for the build. That's quite in line with what automake was doing, just from cmake. I can update my PR and push it again if you want me to?

@emmenlau thanks for the info, please feel free to.

currently i have not yet added library building part into this pull request so it only builds and tests the compiler - the library building part will be added later (possibly not by me). i'm currently mostly focusing on bring up the autoconf part where the approach is split and conquer instead of the original monolithic approach (of preparing all env for all langs).

[ctubbsii]

These changes are CI only, and everything's still passing, so I see no reason not to merge this.