multi form parameter support

[amaskara-dd]

What does this PR do?

Additional Notes

Review checklist

Please check relevant items below:

• This PR includes all newly recorded cassettes for any modified tests.

• This PR does not rely on API client schema changes.

  • The CI should be fully passing.

• Or, this PR relies on API schema changes and this is a Draft PR to include tests for that new functionality.

  • Note: CI shouldn't be run on this Draft PR, as its expected to fail without the corresponding schema changes.

[datadog-datadog-prod-us1]

⚪ Code Quality Violation

Suggested change

	:match_requests_on => [:method, :host, :safe_path, :ignore_query_param_ordering, :body_as_json, :safe_headers],
	:match_requests_on => %i[method host safe_path ignore_query_param_ordering body_as_json safe_headers],

Consider using the %i syntax instead (...read more)

The rule "Prefer %i to the literal array syntax" is a guideline that encourages the use of the %i syntax for arrays of symbols. This is a part of the Ruby style guide that aims to promote conciseness and readability.

Symbols are immutable, reusable objects often used in Ruby instead of strings when the value does not need to be changed. When declaring an array of symbols, using the %i syntax can make your code cleaner and easier to read.

To adhere to this rule, instead of declaring an array of symbols using the literal array syntax like [:foo, :bar, :baz], use the %i syntax like %i[foo bar baz]. It's a good practice to consistently use %i for arrays of symbols as it enhances code readability and maintainability.