Missing guide: Osquery/Fleetd release upstream

[pacamaster]

There currently seems to be a documentation gap with regards to "what osquery version is fleetd/orbit on?" or a way to track if current osquery fixes made it into a fleetd release and the process Fleet takes to release.

Some resources https://github.com/fleetdm/fleet/blob/635ecc3e77e7989af50a1122b8ebf0d35c6c429a/tools/tuf/README.md https://github.com/fleetdm/fleet/blob/main/orbit/CHANGELOG.md https://github.com/fleetdm/fleet/blob/main/orbit/TUF.md

Proposed wordings

• Fleet manually manages osquery releases (then link to process tuf README or explain)
• Fleet chooses to lock in a specific version, or use stable or edge channels
• Fleet keeps a close eye on osquery releases, when they're considered good we manually promote them to stable
• you can check the current released version for each channel: https://github.com/fleetdm/fleet/blob/main/orbit/TUF.md (this gets automatically updated)

Added to customer-success FAQ document if think would be better placed there.

[JoStableford]

Related to a Slack conversation

[lukeheath]

@pacamaster @sharon-fdm Let's discuss. I'm not sure we need a full guide for this. We outline how and when we update osquery in the engineering handbook.

[fleet-release]

In the cloud city, Guide missing, path unclear, Fleet needs a bright star.

Osquery's updates, locked in Fleet's gentle grasp, Stability ensured.

Version, tracked and known, In a glass city, it shines, Fleet's promise, user's trust.

[sharon-fdm]

We have a training video folder for addressing Releasing Agent Components @lucasmrod, do you have any written document for any of the topics presented there?

cc: @lukeheath @pacamaster