LPS-47337 Use ivy.xml files for test dependency resolution

We have configurations in place, so we can have all dependencies
declared in ivy.xml files.
Besides, test dependencies from the ivy.xml from the @{module.dir}
were not taken into account, so it was not possible for modules to
specify their test dependencies.

With this change we set to resolve test dependencies from SDK/ivy.xml
and module/ivy.xml using ivy.resolve.transitive.dependencies.test
property to govern transitivity.
LPS-47337 Resolve dependencies from the SDK and from the module

Since we are always executing resolve before resources there is no need
to pass file or transitive attributes. These are not taken into account
and can be misleading since it may appear that we have path executions
in which ivy:resolve has not been called.

We don't need to specify conf either since we are only resolving test in
the previous calls to resolve.
LPS-47337 This is already being done in compile-test-cmd

And compile-test-cmd is being called always before. Since we don't
support nothing like runtime dependencies from the moment we don't need
to add anything here.
LPS-47337 Move SDK test dependencies to ivy.xml using test
configuration.
LPS-47337 SF
LPS-47337 SF
LPS-47337 Regen
LPS-45607 Inherit configurations from SDK ivy.xml
LPS-45607 We use junit arquillian extension
LPS-45607 We are using a remote tomcat 7 adapter
LPS-45607 We import liferay arquillian extensions for building artifacts
LPS-45607 Update ivy.xml.MD5
LPS-45607 Not needed in default cases
LPS-45607 Sort by conf, then name
LPS-45607 Match core
LPS-45607 Regen
LPS-46840 Add JARs for converting Markdown to HTML
LPS-46840 Use ivy for dependency management
LPS-46840 this now defaults to true
LPS-48112 Apply latest jar