Separate build and input files

[JamesMBligh]

Description
To allow for better visibility of the changes between different versions of the standards it may be advantageous to separate out the scripts and tooling used to build the publishable version of the standards and the raw input swagger and markdown files that actually make up the standards themselves.

Related Work Items

• Separate out the build tooling into a separate repository so that only the raw input files remain in standards and standards-staging
• Create a github action that to can be used build the publishable version from the raw files for remote publishing
• Create a build script that can be used to build the publishable version from the raw files for local review

[perlboy]

It is unclear how separating build tooling from the source aligns with commonly adopted engineering practices. It's also unclear if this is even possible as the Standards currently intermingle build with spec. This approach appears to be the inverse of what has been requested and doesn't appear to have community support for doing so.

Once again, as a member of the community, I oppose this change.