[#620] Add support for optional attach parameter to disable artifact attachment

[peter277]

Add support for optional attach parameter to disable artifact attachment

fixes #620

Checklist

• Make sure there is a GitHub issue filed
  for the change (usually before you start working on it). Trivial changes like typos do not
  require a GitHub issue. Your pull request should address just this issue, without
  pulling in other changes.
• Each commit in the pull request should have a meaningful subject line and body.
• Format the pull request title like [#<num>] - Fixes bug in ApproximateQuantiles,
  where you replace #<num> with the appropriate GitHub issue. Best practice
  is to use the GitHub issue title in the pull request title and in the first line of the
  commit message.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Run mvn clean verify to make sure basic checks pass. A more thorough check will
  be performed on your pull request automatically.
• You have run the integration tests successfully (mvn -Prun-its clean verify).

If your pull request is about ~20 lines of code you don't need to sign an
Individual Contributor License Agreement if you are unsure
please ask on the developers list.

To make clear that you license your contribution under
the Apache License Version 2.0, January 2004
you have to acknowledge this by using the following check-box.

• I hereby declare this contribution to be licenced under the Apache License Version 2.0, January 2004

• In any other case, please file an Apache Individual Contributor License Agreement.

[slawekjaranowski]

simple test will be appreciated

[peter277]

simple test will be appreciated

I have added a new integration test attach_skip to this pull request to test the new parameter's behaviour. Would appreciate your review.

[peter277]

Hi Team - just checking in to see if there’s anything I can do to help move this PR forward? Happy to make adjustments if needed.

CC: @slawekjaranowski, @bmarwell

[peter277]

Thanks @bmarwell for the review - I have incorporated your suggested changes into the branch.

[bmarwell]

I'd remove the last if-else, but works for me.

[slawekjaranowski]

we can simply use a groovy assert

https://groovy-lang.org/semantics.html#_power_assertion

but it is not a blocker for it

[peter277]

Hi Team - just checking in to see if there’s anything else needed before this PR can be merged? Do I need to sign an individual contributor license agreement, given that the change only adds a flag?

Was hoping there might be a release in the near future including this change so that I could start using it.