Add ability to release @fluid-internal/client-utils package

[jatgarg]

Description

Add ability to release @fluid-internal/client-utils package

[alexvy86]

I think it's fine to unblock quickly but let's capture an ADO item to change this to have an explicit list of the ones we don't want to publish, so we don't have to manually add future @fluid-internal packages here when we create them.

Not sure if this is necessary or would work by default, but we probably want to update the lines right above the change to also create an entry in .npmrc for the @fluid-internal scope. In line 42 we do it for the case of publishing packages internally; when publishing externally we'll want to use feedName instead of devFeedName so they go to npm, just like all the other scopes in lines 50-52.

[alexvy86]

Another set of eyes would be ideal, but I think this is correct

[jatgarg]

I think it's fine to unblock quickly but let's capture an ADO item to change this to have an explicit list of the ones we don't want to publish, so we don't have to manually add future @fluid-internal packages here when we create them.

Not sure if this is necessary or would work by default, but we probably want to update the lines right above the change to also create an entry in .npmrc for the @fluid-internal scope. In line 42 we do it for the case of publishing packages internally; when publishing externally we'll want to use feedName instead of devFeedName so they go to npm, just like all the other scopes in lines 50-52.

I think this is a temporary change as once we divide internal and private packages, then we need to change this and publish all internal packages and block private packages