feat(bit-remove): introduce soft-remove

[davidfirst]

Introduce a new flag --soft for bit remove, which does the following:

• locally, the component is removed from the filesystem but kept on .bitmap with a config removed: true of teambit.component/remove aspect.
• upon tag, the component is removed from the .bitmap file.
• upon export, the component is pushed to the remote as is with the removed: true config, so on the remote we know to treat this component as deleted.
• "bit list " - doesn't show deleted components
• "bit import scope/*" - doesn't import deleted components.
• "bit import - imports the component. This is how a deleted component can be recovered.
• on lane, a deleted component won't be merged to main and won't be imported upon bit lane import.

This approach is safer than bit remove --remote, because the component objects are still on the remote and it's recoverable.

See here for more info: #6338