Do not include Spamcheck with the SLES12 package

What does this MR do?

Do not include Spamcheck with the SLES12 package

- Removes Spamcheck and its helper Spamclassifier from the SLES12
  package because SLES 12 uses an older version of RPM that has a much
  smaller available size in the RPM headers. This older version can not
  support the total number of files shipped and there are not enough
  files to remove to fix it other than removal of a package. Confirmed
  with Martin Brümmer that there is no usage, thus no customer impact.

Related https://gitlab.com/gitlab-org/omnibus-gitlab/-/work_items/9716

Changelog: removed

Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Related issues

Related SLES-12.5 EE build jobs fail (#9716) • Robert Marshall • 18.11

Checklist

See Definition of done.

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

Required

• MR title and description are up to date, accurate, and descriptive.
• MR targeting the appropriate branch.
• Latest Merge Result pipeline is green.
• When ready for review, MR is labeled workflowready for review per the Distribution MR workflow.

For GitLab team members

If you don't have access to this, the reviewer should trigger these jobs for you during the review process.

• The manual Trigger:ee-package jobs have a green pipeline running against latest commit.
• If config/software or config/patches directories are changed, make sure the build-package-on-all-os job within the Trigger:ee-package downstream pipeline succeeded.
• If you are changing anything SSL related, then the Trigger:package:fips manual job within the Trigger:ee-package downstream pipeline must succeed.
• If CI configuration is changed, the branch must be pushed to dev.gitlab.org to confirm regular branch builds aren't broken.

Expected (please provide an explanation if not completing)

• Test plan indicating conditions for success has been posted and passes.
• Documentation created/updated.
• Tests added.
• Integration tests added to GitLab QA.
• Equivalent MR/issue for the GitLab Chart opened.
• 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.