[BUG] Module names in UMD builds do not match
### Describe the bug

Each package's UMD build adds a property to `self` that is different than what the other packages' UMD builds expect; for example:
```js
// in `@tsed/schema/lib/browser/schema.umd.min.js`
// e === self, t === factory
e.schema=t(e["@tsed/core"],e["change-case"])

// in `@tsed/core/lib/browser/core.umd.min.js`
// t === self, e === factory
t.core=e()
```
When `@tsed/schema` executes in a browser, it looks for `self["@tsed/core"]`, which doesn't exist (although `self.core` does).

### To Reproduce

1. Use Webpack to bundle `@tsed/schema`
2. Execute the bundle in a browser
3. See an error like `e.DecoratorTypes is undefined` (where `e` is supposed to be the exports from `@tsed/core`)

### Expected behavior

No error

### Code snippets

_No response_

### Repository URL example

_No response_

### OS

macOS

### Node version

Node v18.17.1

### Library version

v7.39.0

### Additional context

_No response_