Log file names should be consistent across CLI, and web

[gayanW]

Before:

| File           | Status                  |
|----------------|-------------------------|
| app.log        | ✓ Recorded successfully |
| nested-app.log | ✓ Recorded successfully |

After:

| File             | Status                  |
|------------------|-------------------------|
| app.log          | ✓ Recorded successfully |
| nested/app.log   | ✓ Recorded successfully |

The backend code is also modified, so that the web UI shows the same name as the CLI output.
https://github.com/launchableinc/mothership/pull/13261

[ono-max]

Oh, did you solve this problem as well?

[gayanW]

Sorry I forgot the original reason that we decided to replace spaces with '-'.
But I remember that you said file names like foo-.log are not ideal, so that we might have to change it.

[ono-max]

That was because 500 error was occurring when the whitespace was included. So, we first need to modify the intake side to accept the whitespace. Then, we need to delete this method.

[gayanW]

Sorry let me add it back, until we figure out how to handle white spaces in backend.

[ono-max]

@gayanW

CI is failing now.

[gayanW]

@ono-max Fixed.