Refactor Transparency value handbook content

Why is this change being made?

I think the Transparency value text could flow more logically. Refactor existing content such that:

• main body defines transparency and why the value is important
• Public by default provides examples that demonstrate this approach
• Not public provides examples of when information isn’t public, what to do if you think something should change state

Future iterations: I tried to make as few text changes as possible to reduce MR complexity. I plan to make text changes in future MRs.

Author Checklist

• Provided a concise title for this Merge Request (MR)
• Added a description to this MR explaining the reasons for the proposed change, per say why, not just what
  • Copy/paste the Slack conversation to document it for later, or upload screenshots. Verify that no confidential data is added.
• Assign reviewers for this MR to the correct Directly Responsible Individual/s (DRI)
  • If the DRI for the page/s being updated isn’t immediately clear, then assign it to one of the people listed in the Maintained by section on the page being edited
  • If your manager does not have merge rights, please ask someone to merge it AFTER it has been approved by your manager in #mr-buddies
• If the changes affect team members, or warrant an announcement in another way, please post an update in #whats-happening-at-gitlab linking to this MR
  • If this is a change that directly impacts the majority of global team members, it should be a candidate for #company-fyi. Please work with internal communications and check the handbook for examples.

---