Add FAQ to the deploying section of the docs for allowing WebSockets

[DominusKelvin]

Goal

This FAQ should point to users experiencing broken live queries or policies queries on their Fleet Instance to check if WebSocket is allowed in their deployment of Fleet.

How?

• Add FAQ titled Why aren't my live queries or policies queries working?
• Answer the question

[lucasmrod]

@lukeheath Was this closed accidentally? (Am looking for such docs.)

[lukeheath]

@lucasmrod Yes, some PRs and issues tagged 4.16 accidentally got closed when cycling out the milestone. Reopened!

[lucasmrod]

Thanks!

Marking #6049 as related.

[lucasmrod]

Also take a look at https://osquery.slack.com/archives/C01DXJL16D8/p1656964075641729

I assume this is related to our infrastructure security controls regarding websocket routes. In my deployment I have to specify which routes are websockets (currently only /api/v1/fleet/results). So my real question is, what routes do I need to allow for Goquery to work properly? (If the issue is about that)

Users should also whitelist /api/latest/fleet/results (for fleetctl goquery command to work).

[noahtalerman]

Hey @DominusKelvin I saw that this prioritized doc improvement got lost of the 🪂 Community board (now retired).

I moved this issue to the "Ready" column in the 🚀 Release board.

cc @zhumo