Added spaces to disallowed char for working dir

[prithvi081099]

#40546, For this issue I have added space to disallowed char.

Why are these changes needed?

Related issue number

Checks

• I've signed off every commit(by using the -s flag, i.e., git commit -s) in this PR.
• I've run scripts/format.sh to lint the changes in this PR.
• I've included any doc changes needed for https://docs.ray.io/en/master/.
  • I've added any new APIs to the API Reference. For example, if I added a
    method in Tune, I've added it in doc/source/tune/api/ under the
    corresponding .rst file.
• I've made sure the tests are passing. Note that there might be a few flaky tests, see the recent failures at https://flakey-tests.ray.io/
• Testing Strategy
  • Unit tests
  • Release tests
  • This PR is not tested :(

[rynewang]

hmm, I'd say OK for this. But maybe a more future proof (what if there are other strange chars in the future?) is to:

1. use f"{protocol}_{sha256(name_stem)}.{name_suffix}"
2. use f"{protocol}_{urlsafe_base64(name_stem)}.{name_suffix}"

would you mind to give it a try?

[rynewang]

Merging this, leaving the comment in #46767 (comment) as a future todo.