LPS-47337 These are not common to all plugins

These dependencies are only suitable for legacy plugins. We'd better
specify this on a per plugin basis.
LPS-47337 Do not cache artifacts that come from local repositories
LPS-47337 new property to govern transitivity on test dependencies.

We default this to true because test dependencies are not copied to any
directory and test infrastructure has a big dependency graph.
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