Add minimum system consideration to MR acceptance checklist

What does this MR do and why?

Describe in detail what your merge request does and why.

As discussed in !117637 (comment 1391794101), adding minimum system requirement consideration to MR acceptance checklist. So

Distribution, Geo, Infrastructure and Reference Architecture groups need to be aware of upcoming changes before they are implemented to ensure that maintenance and cost for self-managed customers is considered at the very beginning. Few recent examples when this review happened late in the chain - ClickHouse and DB size increase - where such process would have been beneficial. (From https://gitlab.com/gitlab-org/gitlab/-/issues/403859#note_1351253785)

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.