Project structure can be broken when workspace's name and namespace are same

[mt0erfztxt]

Describe the bug
Not all symlinks created in workspace when its name and namespace are same and contains dashes.

To Reproduce
Steps to reproduce the behavior:

$ lein polylith create w foo-bar foo-bar
$ cd foo-bar
$ lein polylith create s api-server api-server
Warning. Could not create symbolic link '/path/to/foo-bar/systems/api-server/src/foo_bar/api_server': /path/to/foo-bar/systems/api-server/src/foo_bar/api_server
Warning. Could not create symbolic link '/path/to/foo-bar/environments/development/src/foo_bar/api_server': /path/to/foo-bar/environments/development/src/foo_bar/api_server
Warning. Could not create symbolic link '/path/to/foo-bar/environments/development/test/foo_bar/api_server': /path/to/foo-bar/environments/development/test/foo_bar/api_server
$ lein polylith info
interfaces:
components:
bases:
  api-server *
systems:
  api-server *
environments:
  development

Expected behavior
All symlinks created

$ lein polylith create w foobar foobar
$ cd foobar
$ lein polylith create s api-server api-server
$ lein polylith info
interfaces:
components:
bases:
  api-server *
systems:
  api-server *
    api-server *   -> base
environments:
  development
    api-server *   -> base

Operating System:

• OS: Linux Mint
• Version: 19.1 Tessa

Versions:

• Leiningen: 2.8.3
• Java: 1.8.0_201
• Polylith: 0.2.2

Additional context
As shown in Expected behavior issue doesn't appears when workspace name doesn't contain dashes.