shore-config - test-remote command using shore config with the correct profile

## Summary

Original Author: @dkirillov
`shore test-remote` command should now use the E2E config specified in the shore config.

Specifically, in the shore config it is stored under the following path - `profiles.[profile-name].e2e`. Example shore config:

```yml
renderer:
...

executor:
...

profiles:
default:
application: \"myAppName\"
pipeline: \"awesome-pipeline\"
render: ... # Path or Object
exec: ... # Path or Object
e2e: ... # Path or Object

```

What is present in the profile could either be the full E2E config object (in-line config), or a path to the `E2E.yml` file (external config). Either or is allowed and should be used.

## Motivation

## Describe alternatives you've considered

## Additional context

Start at the implementation of the `shore test-remote` command and trace how it currently obtains its E2E configuration. Check the `profiles.[profile-name].e2e` value in the shore config, including inline objects and paths to `E2E.yml`. Done means both forms are used for the selected profile when running `shore test-remote`.

Written by the indexing model from the issue text.