Mention non-ticket work in baseline guidance

Why is this change being made?

I think non-ticket work should be mentioned here explicitly, this would be in accordance with prioritizing it a bit higher in Reflect current reality of how Support work is ... (!119362 - merged) as well. Also some minor wording changes.

Originally this MR had a larger scope, preserving the text here:

- Finally, removing the hardcoded baseline numbers: - They are most likely somewhat outdated, I remember that came up in a 1:1 many many months ago once before - The dashboard with dynamically updating baselines does not actually have values for "number of first responses", it only has public comments, internal comments and solved.

If we really do value "number of first responses" as a metric, we should add it to this dynamic dashboard. That should be possible, considering that the individual dashboards have a FRT number. I'm not sure if we really want that as a metric, though. Unless it is worded imprecisely, it's not really what we want.

What we want is: FRTs in the sense of "first response and assigned". But I'm also not convinced that this combined metric is all that valuable. Why should an assignment not count if I take it after someone else sent the FRT? In my opinion the existing metrics in the dynamic dashboard (public comments, internal comments, solved) are more than enough to gauge your performance with tickets. If we want to add another one, I'd make it a generic "Assignments" one, not coupled to FRTs. (That also exists already in the individual one.) That is all something that could be discussed at length in a follow-up iteration, though. For now, I think that removing the hardcoded numbers in favor of only linking to the dynamic ones is an improvement.

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, and the content is SAFE
• 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
  • The when to get approval handbook section explains the workflow in more detail
• If the changes affect team members, or warrant an announcement in another way, please consider posting 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.

---