[Request]: container machine run should spawn a login shell

### Feature or enhancement request details

Default behaviour of `container machine run` is to spawn an interactive shell inside container machine. Help info on `container machine run --help` even states following:

```
ARGUMENTS:
Command to run (default: login shell)
```

My observed behaviour is that interactive shell spawned is not a login shell. This has a number of drawbacks how interactive shell is initialised (both bash and zsh will not source "profile" rc files). This is in contrast to say connection via SSH to a running machine instances.

I would argue that shell should be login shells, or at least there should be a way to configure this per container machine.

```
container CLI version 1.0.0 (build: release, commit: ee848e3)
```

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start at the `container machine run` command and compare its default shell behavior with the `container machine run --help` description and SSH connections to running machine instances. Check how interactive bash and zsh initialization handles profile rc files, then verify that the default shell is a login shell or that the requested configuration is available per container machine.

Written by the indexing model from the issue text.