shore-config - save command using shore config with the correct profile

## Summary

Original Author: @dkirillov
`shore save` command should now use the render config specified in the shore config.
(Save renders and publishes the pipeline - so the same `render.yml` is used)

Specifically, in the shore config it is stored under the following path - `profiles.[profile-name].render`. 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 render config object (in-line config), or a path to the `render.yml` file (external config). Either or is allowed and should be used.

## Motivation

## Describe alternatives you've considered

## Additional context

Start at the `shore save` command and trace how it selects the render configuration. Check the profile at `profiles.[profile-name].render` and verify both inline objects and paths to `render.yml` are handled. Done means save renders and publishes the pipeline using the profile's render configuration.

Written by the indexing model from the issue text.