DOCS: Improve Mouse & ButtonControl API docs

[stefanunity]

Description

Mouse:
DONE -1 for having related links (not recommended for this API type) on current
DONE -1 for insufficient summary length (threshold is 35) each for leftButton, middleButton, rightButton
DONE -1 for using the value tag (not recommended; use the remarks tag instead) each for backButton, clickCount, current, forwardButton, leftButton, middleButton, rightButton, scroll
DONE -2 for insufficient remarks length (threshold is 120) on WarpCursorPosition(Vector2)
DONE -3 for no related links (required for this API type) on Mouse
DONE -4 for missing parameter description for the 'eventPtr' parameter on OnStateEvent(InputEventPtr)
DONE -6 for no code samples (required for this API type) on Mouse

Not done, left for future person:
-4 for no code samples (required for this API type) each for FinishSetup(), MakeCurrent(), OnAdded(), OnNextUpdate(), OnRemoved(), OnStateEvent(InputEventPtr), WarpCursorPosition(Vector2)
-4 for no remarks (required for this API type) each for OnAdded(), OnNextUpdate(), OnRemoved(), OnStateEvent(InputEventPtr)

ButtonControl:
DONE -1 for using the value tag (not recommended; use the remarks tag instead) each for pressPoint, isPressed, pressPointOrDefault, wasPressedThisFrame, wasReleasedThisFrame
DONE -bring back removed links as sentence?

Testing status & QA

No errors on CI

Overall Product Risks

None

Checklist

Before review:

• Changelog entry added.
  • Explains the change in Changed, Fixed, Added sections.
  • For API change contains an example snippet and/or migration example.
  • JIRA ticket linked, example (case %%). If it is a private issue, just add the case ID without a link.
  • Jira port for the next release set as "Resolved".
• Tests added/changed, if applicable.
  • Functional tests Area_CanDoX, Area_CanDoX_EvenIfYIsTheCase, Area_WhenIDoX_AndYHappens_ThisIsTheResult.
  • Performance tests.
  • Integration tests.
• [*] Docs for new/changed API's.
  • Xmldoc cross references are set correctly.
  • Added explanation how the API works.
  • Usage code examples added.
  • The manual is updated, if needed.

During merge:

• Commit message for squash-merge is prefixed with one of the list:
  • NEW: ___.
  • FIX: ___.
  • DOCS: ___.
  • CHANGE: ___.
  • RELEASE: 1.1.0-preview.3.

After merge:

• Create forward/backward port if needed. If you are blocked from creating a forward port now please add a task to ISX-1444.