Fix Ruby 2.7 deprecation warnings for JUnit parser

Ref: #257438 (closed)

What does this MR do?

In Ruby 3.0, positional arguments and keyword arguments will be separated. In Ruby 2.7, deprecation warnings related to keyword arguments show up.

Explicitly specify passing keyword arguments instead of a Hash object by using double splat operator.

Since Junit#parse! expects kwargs, updated the spec to pass options as keyword arguments.

Before	After

Does this MR meet the acceptance criteria?

Conformity

• [-] Changelog entry
• [-] Documentation (if required)
• Code review guidelines
• [-] Merge request performance guidelines
• [-] Style guides
• [-] Database guides
• [-] Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• [-] Tested in all supported browsers
• [-] Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• [-] Label as security and @ mention @gitlab-com/gl-security/appsec
• [-] The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• [-] Security reports checked/validated by a reviewer from the AppSec team