Add possibility to include multiple non primitive types in an array

[ochnygosch]

Description

If an array is defined for an entity it is currently not possible to
include different types of non primitive types in the same array.

E.g. it is not possible to add a product, whose "custom_attributes" field
should contain attributes that have a primitive type (e.g. url_key) and an
array type (e.g. category_ids)

This PR adds the ability to define multiple non primitive types for an array
type.

The definition of the CreateProduct request in
magento-catalog/Test/Mftf/Metadata/product-meta.xml could be changed to

<array key="custom_attributes">
  <value>custom_attribute_array</value>
  <value>custom_attribute</value>
</array>

Contribution checklist

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/verification tests (if applicable)
• All automated tests passed successfully (all builds on Travis CI are green)
• Changes to Framework doesn't have backward incompatible changes for tests or have related Pull Request with fixes to tests

[magento-cicd2]

All committers have signed the CLA.

[coveralls]

Coverage increased (+1.4%) to 53.639% when pulling 491802c on ochnygosch:fDiverseArray into 3c7ed4b on magento:develop.

[KevinBKozan]

Hey @ochnygosch, thank you for your submission! We created a ticket internally for reviewing your PR, and will be updating you with feedback and progress on this PR.

[tomreece]

Hi @ochnygosch! This change looks good to me after some manual testing.
But will you please add a unit test for this change?
See OperationDataArrayResolverTest.php for examples.

[tomreece]

Hi @ochnygosch, thank you very much for adding unit tests to your change.

We have one last thing to resolve,
The Travis builds are failing due to a Cyclomatic Complexity error introduced in the function that you modified resolveOperationDataArray().

Do you see this error in the Travis results?

Can you fix this Cyclomatic Complexity error without simply suppressing it? Give it a shot and if you can't resolve it then we will discuss whether to allow a suppression of it or not.

Thank you for your time and contribution to MFTF.

[tomreece]

Hi @ochnygosch -- Just checking in,

You don't have to fix the cyclomatic complexity warning. I will do this for you.

But we do need you to sign the Adobe CLA. Thanks!

[tomreece]

@KevinBKozan After code freeze, merge PR #490
instead of
#433