Update dnsmichi README - refactor for clarity, readability and update title

Why is this change being made?

💡 Provide a detailed answer to the question on why this change is being proposed, in accordance with our value of Transparency.

Please add the details saying why, not just what in this section. Example: We have discussed the topic in Slack - (copy of Slack conversation). The current process is not efficient, this MR makes the description of X more clear, and helps move Y forward.

This merge request updates Michael Friedrich's personal README page to reflect his promotion from Staff Developer Advocate to Principal Developer Advocate. The changes improve the document's readability and organization by restructuring sections, adding formatting like bold text for emphasis, and streamlining the content. Key updates include a reorganized "About me" section with better flow, consolidated work values with clearer explanations, and removal of the separate "Strengths and weaknesses" section in favor of integrating those points into how he applies GitLab's values. The update also adds a transparency note mentioning that GitLab Duo AI assisted with editing while maintaining his authentic voice. Overall, the changes make the document more concise and easier to read while preserving all the important information about how to work with Michael.

Kudos to Duo Agentic Chat for being a great collaboration partner, validating and iterating.

Author and Reviewer Checklist

Please verify the check list and ensure to tick them off before the MR is merged.

• 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, and the content is SAFE
• Assign reviewers for this MR to the correct
  • The when to get approval handbook section explains when DRI approval is required
  • The who can approve handbook section explains how to identify the DRI
  • If the MR does not require DRI approval, consider asking someone on your team, such as your manager.
  • The approver may merge the MR. If they approve but don't merge, you can merge.
• For transparency, share this MR with the audience that will be impacted.
  • Team: For changes that affect your direct team, share in your group Slack channel
  • Department: If the update affects your department, share the MR in your department Slack channel
  • Division: If the update affects your division, share the MR in your division Slack channel
  • Company: If the update affects all (or the majority of) GitLab team members, post an update in #whats-happening-at-gitlab linking to this MR
    • For high-priority company-wide announcements work with the internal communications team to post the update in #company-fyi and align on a plan to circulate in additional channels like the "While You Were Iterating" Newsletter

Commits

• refactor dnsmichi readme #6 (closed), minor + transparency note
• refactor dnsmichi readme #5, move up working with me
• refactor dnsmichi readme #4, about me
• refactor dnsmichi readme #3, experience
• refactor dnsmichi readme, #2 - strength/weaktness
• dnsmichi readme refactor, #1 (closed) - values

---