Add @typespec/streams as direct dependency

[mikeharder]

• Intention is to pin all TSP packages, not just leaf nodes
• Ensures branch "tsp-next" resolves the correct packages

[openapi-pipeline-app]

Next Steps to Merge

Next steps that must be taken to merge this PR:

• ❌ The required check named Protected Files has failed. Refer to the check in the PR's 'Checks' tab for details on how to fix it and consult the aka.ms/ci-fix guide

[openapi-pipeline-app]

PR validation pipeline restarted successfully. If there is ApiView generated, it will be updated in this comment.

[chrisradek]

Should we include @typespec/xml as well? It is used by @typespec/openapi3 as an optional peer just like streams:
https://github.com/microsoft/typespec/blob/72e5c09a306da55a7e19a248beef6413687d25e1/packages/openapi3/package.json#L70-L74

[timotheeguerin]

Should we include @typespec/xml as well? It is used by @typespec/openapi3 as an optional peer just like streams: https://github.com/microsoft/typespec/blob/72e5c09a306da55a7e19a248beef6413687d25e1/packages/openapi3/package.json#L70-L74

ah good point not sure why tis not failing there too

[mikeharder]

Should we include @typespec/xml as well? It is used by @typespec/openapi3 as an optional peer just like streams: https://github.com/microsoft/typespec/blob/72e5c09a306da55a7e19a248beef6413687d25e1/packages/openapi3/package.json#L70-L74

@chrisradek: That's actually not a valid optional peer dep. It needs to be listed under peerDependencies in addition to peerDependenciesMeta. If you fix this bug, then yes we will need to add @typespec/xml.

@timotheeguerin