only/except behaviour when matching both

Description

(especially useful when using templates) If you have an exact match in both the only and except clauses of a job the job should build in my opinion.

Example:

Having a base template for several deployments, which shouldn't execute when using a trigger, thus I have:

except:
  - trigger

as part of the deploy template.

However, a certain deploy should be executed by the trigger, thus I have:

only:
  - trigger

on the job (which includes the except clause from the parent template)

Proposal

have only get a slightly higher priority then except (for the same grade of matches, i.e. except: feat-x shouldn't be overruled by only: feat-*)

Links / references

Current documentation section regarding only/except

Documentation blurb

* If both `only` and `except` contain the same rule, `only` takes precedence