Name already in use

This blocks #7159 from happening.
It's not clear how it happened, but if it happens again, it'll block it
during the tag/snap.

…7238)

… overflows (#7233)

)

This fix reduces the number of repeat installs

…iles (#7234)

## Proposed Changes

- add include to the generated global types folder from the generated
tsconfig files
- add `node_modules/@types` to the `typeRoots` in the generated root
tsconfig file
- reference relative config files with `./` at the beginning (some tools
like TS don't know to use relative path correctly when not start with
`.` or `..`)

…ved components (#7225)

This new command works regardless of the state in the workspace,
specifically tested on the following use-cases:
1. a component was just soft-removed, it wasn't snapped yet, so it's now
in .bitmap with the "removed" aspect entry.
2. soft-removed and then snapped. It's not in .bitmap now.
3. soft-removed, snapped, exported. it's not in .bitmap now.
4. a soft-removed components was imported, so it's now in .bitmap
without the "removed" aspect entry.
5. workspace is empty. the soft-removed component is on the remote.

Writing object files is 16 times faster with this change. See
npm/write-file-atomic#155 for more info.

## Proposed Changes
- update loader-utils to fix audit issue
- update webpack-dev-server for audit issue
- update @teambit/base-react.navigation.link to fix audit issues

…was not found (#7223)

This is an out-of-sync case which apparently we didn't handle.
It happens when a component is exported. One user tagged the exported component locally, committed and pushed, another user clones the repo, gets the .bitmap with the versions according to the tagged one, which only exist on the first-user local but not on the remote.
Until now, in this case, `bit status` was showing the import-pending message, suggesting to import, but `bit import` was throwing `ComponentNotFound` error.
This PR fixes the import to not throw. Instead, in the output it shows the not-found components and suggests running `bit status` to sync the .bitmap back to the remote.

…place extending file name with its abs/relative path (#7221)

## Proposed Changes

- This also fixes issues with pnpm lock file getting changed on the
second bit install when you have custom envs in your workspace

## Proposed Changes

- update the homepage field added to a component's package.json so it reflects the current remote domain (not hard-coded to the old bit.dev domain)

## Proposed Changes

- update loader-utils to fix audit issue
- update webpack-dev-server for audit issue

In some cases, the `Version` object is mutated. For example when merging
with squash or when building on CI.
Currently, the object-writer is not aware of that and treat this object
as immutable. As a result, it's possible that locally a `Version` object
has changed and has the `squashed` prop and `parents` modified, but an
import process that fetched this Version as a dependency of another
component, overrode it.
This PR fixes it by adding a new `modified` property to the `Version`
object and it allows overriding only in case the incoming object is
newer.

… them relative paths (#7212)

## Proposed Changes

- nest typesRoot under compilerOptions
- make typesRoot values relative paths instead of absolute 
- Uniq typesRoot