Bug/Improvement: Add commands to regenerate table schema used by Website/App when modifying specific table schemas to README/docs

[RachelElysia]

Fleet version: (head to the "My account" page in the Fleet UI or run fleetctl --version)

Operating system: (e.g. macOS 11.2.3)

Web browser: (e.g. Chrome 88.0.4324)

---

🧑‍💻  Expected behavior

• Someone pushed a change in schema/tables/screenlock.yml
• I'm working on the same file
• I expected their change to be surfaced to users on the app and website (which uses osquery_fleet_schema.json as a source of truth) as I will be surfacing my changes there as well.

💥  Actual behavior

• The changes that Mo made are not updated to the app or website
  • The changes are not reflected because they did not regenerate the osquery_fleet_schema.json after their changes.

👣 Reproduction steps

1. Make a change to schema/tables/table_name_here.yml like Mo did in Update screenlock table doc to be more explicit about its limitations #12432
2. See that the change is not surfaced in the UI query tables side panel or on the website docs after saving/merging

More info

• This process is not clear and should be clarified in the README. I also fell into the same trap a week ago assuming updating a table here will automatically update the documentation.

[sharon-fdm]

As described by Lucas the way to regenerate the osquery_fleet_schema.json schema is using this command:

cd website
./node_modules/sails/bin/sails.js run generate-merged-schema

[zhumo]

@sharon-fdm @RachelElysia in this case, could this be made into a github action that runs after a merge? (@eashaw)

[zhumo]

If not, then I think we fall back to documentation.

[sharon-fdm]

@zhumo the ability to automate it will be much better. If so, need to prioritize it.
In any case I propose a document fix at #12461 as a w\a (or maybe as a final step)