[http-client-js] Any issues on un-supported spector cases would block automations of new spector cases

[MaryGao]

Currently we leverage the "workspace:" version for spector cases, so any issues on un-supported spector cases would block automations of new spector cases like this one. I can understand this could help update the latest spector cases with no manual effort. But it also coupled new cases adding and js emitters feature support.

• typespec/packages/http-client-js/package.json

  Lines 69 to 70 in cc74c72

  	"@typespec/http-specs": "workspace:^",
  	"@typespec/spector": "workspace:^",

We have two options here: one is to use fixed version for spector's libs. The other is to leverage a whitelist for supported spector cases.

Personally I would prefer to update to fixed versions directly.

[timotheeguerin]

please don't uses another version that's the whole point of being in the workspace. Doing that is going to be a mess as other packages will all be part of the workspace but somehow the test will be outdated. (It was with a diffferent version previously and that broke things even more)

There is 2 cases where this break

• A change that breaks: This is exactly what the setup is desiged to do, it needs to be fixed before merging.
• Adding a new spec that is not supported. This needs a way to exclude for now so it doesn't need to be implemented right now

[MaryGao]

Thanks Tim's information! I notice we already have an exclusion list feature here. So directly close this.