Draft: CI: Only include Allure job on gitlab.com

What does this MR do?

CI: Only include Allure job on gitlab.com

In !3370 (merged) we added the Allure report to merge requests, and only include the CI reference files on gitlab.com.

We need to have that same rule on the CI job that references those CI reference files, so this change ensures that the Allure CI job is skipped if the CI server is not gitlab.com.

Testing

• Branch is pushed to dev to ensure that the Allure job is not included and CI configuration is valid

Author checklist

See Definition of done.

For anything in this list which will not be completed, please provide a reason in the MR discussion.

Required

• Merge Request Title and Description are up to date, accurate, and descriptive
• MR targeting the appropriate branch
• MR has a green pipeline on GitLab.com
• When ready for review, follow the instructions in the "Reviewer Roulette" section of the Danger Bot MR comment, as per the Distribution experimental MR workflow

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes
• Documentation created/updated
• Tests added/updated
• Integration tests added to GitLab QA
• Equivalent MR/issue for omnibus-gitlab opened
• Equivalent MR/issue for Gitlab Operator project opened (see Operator documentation on impact of Charts changes)
• Validate potential values for new configuration settings. Formats such as integer 10, duration 10s, URI scheme://user:passwd@host:port may require quotation or other special handling when rendered in a template and written to a configuration file.