Typo fix & SetCheckPermissions example.

tools/issue-tracking.md - Update guidance on Gitlab labels

Add use statement for definition - hopefully people will know that go…

__Before__: The documentation explains ~5 common labels.  Gitlab actually has ~50
labels.

__After__: The documentation explains ~3 important labels and ~4 *prefixes*.
Each prefix is given with a definition and example, and there are links
to the full lists.

__Comment__: The link goes to https://lab.civicrm.org/dev/core/-/labels
though arguably https://lab.civicrm.org/groups/dev/-/labels might be better.
However, there a dozen or so labels which (rightly or wrongly) only show up
in `dev/core`, so `dev/core` gives the more comprehensive listing.

Add link to Abandoned Extensions page/info.

update hook_civicrm_export signature

Further improvements to l10n format in hook_civicrm_permission docume…

Further clarification of financial items

improve suggestions re custom reports

Edits to APIv4 section

Document regen.sh

Formatting improvements and add code comments on Order API + fix broken URL

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

update my repo from upstream master

Document BuildKit EoL Policy

provided best practice advice on report extension creation

Co-Authored-By: Mikey O'Toole <mikey@mjco.uk>

pull recent changes from upstream master

This table is not relevant for several install methods (Vagrant/Docker/Generic).

For Ubuntu/Debian, I think it's useful information, but it's a bit
overwhelming, and what we're basically doing is elaborating on a couple
words (*it needs to be a __recent__, supported version of Ubuntu/Debian -
which is specifically yadda yadda...*).

If one is oblivious to this content and runs the install script on an
unsupported version of Ubuntu/Debian, that should be safe -- since the first
thing it does is to verify compatibility.

Note: not trying to bury - the next commit will call this out a bit more.