[trainer] report run destination as testsuite properties

[kronenthaler]

Checklist

• I've run bundle exec rspec from the root directory to see all new and existing tests pass
• I've followed the fastlane code style and run bundle exec rubocop -a to ensure the code style is valid
• I see several green ci/circleci builds in the "All checks have passed" section of my PR (connect CircleCI to GitHub if not)
• I've read the Contribution Guidelines
• I've updated the documentation if necessary.

Motivation and Context

When running fastlane over multiple destinations (aka, devices and OS versions) it's impossible to know in the final report which destination failed.

Description

The information about the destination is already available in the xcresult bundle, but it was ignored during the parsing. This PR introduces the basic types and hooks them into the parsing flow.
That allow the action type to have access to the test suites (test_ref) and the run_destination. However, the code needed refactoring as it was processing everything in batch ignoring on what test suite it belonged to. Thus, the code was refactor to process each test suite as a single unit, allowing to pass the run destination information along.
Then the template was updated to reflect the new properties in the test suite if they are available.

Testing Steps

All unit tests and fixtures were updated to reflect the new changes.

[google-cla]

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

[kronenthaler]

Any reviewers for this feature?