Create a binary to pull tables from fleetd without other fleetd functionality

[zayhanlon]

User story:
As a customer who uses plain osquery, there are tables from other sources and fleetd that are useful to be pulled in without the added functionality of fleetd that's already provided by the osquery agent.

**Technical spec from @zwass :"

• Create a binary that the sole purpose is to provide those tables without the rest of fleetd

Longer term or possible phase 2 depending on estimation:

• Ongoing maintenance to keep providing tables
• Design in such a way that new tables can automatically go into this

Customer context: Check their Slack channel or contact @zayhanlon

[zayhanlon]

@lucasmrod Here's the issue I created for the discussion we had on the estimation call yesterday. Please feel free to connect with Zach via Slack or directly in this issue with your questions!

[zayhanlon]

@edwardsb Also to review and consult with Lucas/Zach.

[lucasmrod]

Basically build a statically compiled osquery extension (.ext) that holds all the fleetd (Orbit) tables.
Estimation: 2 pts (0.5 points code changes, 0.5 points for automation to build the executable, 1 extra point for testing multi-platform and make this future proof if we add more tables.)

Maybe we can start with macOS first? (to reduce scope even more).

[fleet-release]

Fleetd tables' grace,
In osquery they dance,
Binary embrace.