Reorganize doc guidelines into multiple pages; update style guide

The existing doc guidelines page attempts to combine too many different
topics at once and includes information that does not pertain directly
to the documentation. This reorganization is intended to make each type
of information easier to find. For example, some have found it difficult
to find the documentation style guidelines (see, e.g.,
QubesOS/qubes-issues#6701#issuecomment-875875610). This reorganization
allows us to assign more specific titles to each page.

General changes:
- Create new page for contribution instructions
- Create new page for website style guide
- Create new page for continuous integration
- Rename existing "style guide" to "visual style guide" in order to
  avoid ambiguity with new doc and website style guides
- Retain existing page solely for doc style guide
- Update page names and permalinks
- Update existing links
- Improve language

Doc style guide changes:
- Add section on using sentence case in headings
  (see QubesOS/qubes-issues#6756 and #1173)
- Improve section organization
- Clarify language

In order to better preserve the Git history of each file, file renames
will be handled in a separate commit.

introduction/support.md

@@ -124,7 +124,7 @@ contributions](/doc/code-signing/).
 For example, you might find it easier to trust advice from someone who has a
 proven track record of [contributing software
 packages](/doc/package-contributions/) or [contributing to the
-documentation](/doc/doc-guidelines/). It's unlikely that individuals who have
+documentation](/doc/how-to-edit-the-documentation/). It's unlikely that individuals who have
 worked hard to build good reputations for themselves through their
 contributions over the years would risk giving malicious advice in signed
 messages to public mailing lists. Since every contribution to the Qubes OS
@@ -217,7 +217,7 @@ not a discussion
 forum](/doc/issue-tracking/#the-issue-tracker-is-not-a-discussion-forum).)
 Likewise, if you see that something in the documentation should be changed,
 don't simply point it out in a discussion venue. Instead, [submit the
-change](/doc/doc-guidelines/).
+change](/doc/how-to-edit-the-documentation/).
 
 ### Moderation