Description

remove deprecated --no-workspace-strict-match option

Motivation and Context

When we first introduced the workspace: protocol, it wasn't strict and we soon after introduced the strict mode so that it follows more closely the pnpm/yarn workspace: protocol. I don't see any user who wouldn't want the script mode so the no strict was deprecated a while back and this PR removes that code and we now only assume strict match

The strict match will do the following:

{
  "dependencies": {
    "foo": "workspace:*",
    "bar": "workspace:~",
    "qar": "workspace:^",
    "zoo": "workspace:^1.5.0"
  }
}

and published as the following strict match

{
  "dependencies": {
    "foo": "1.5.0",
    "bar": "~1.5.0",
    "qar": "^1.5.0",
    "zoo": "^1.5.0"
  }
}

the non-strict match, was basically going to publish everything (except foo) as ~1.5.0 which is probably not what any user would want.

How Has This Been Tested?

Types of changes

• Chore (change that has absolutely no effect on users)
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have removed tests to cover my changes.
• All new and existing tests passed.