refactor(server): Remove dependency on common-utils

[alexvy86]

Description

This is an experiment around removing the common-utils dependency in the server/routerlicious release group.

There are 3 major "approaches":

• A couple of things were used in a single package or a very few places; those I just moved to live in the package that used them.
• Some things were used in many packages, but stayed firmly on the server side, thus guaranteed to be running in a NodeJS environment. Those I moved to @fluidframework/server-services-core since almost everything else in the server group depends on it.
• Some things were used in several packages but in particular they were used in @fluidframework/server-services-client, which the client release group depends on, and thus they could end up running in NodeJS or in the browser. Those I moved to @fluidframework/server-services-client itself, and re-exposed them from there for the rest of the packages that need them. Similarly to @fluidframework/server-services-core, @fluidframework/server-services-client is a package that almost everything else in the server group depends on.
  • In particular, things related to Buffer, encoding (which leverages Buffer), and file hashing, moved here.

One thing stood out while moving: TypedEventEmitter. It ended up copied in two different places (@fluidframework/server-sevices-core and @fluidframework/protocol-base) because neither depends on the other. It's built on top of several types which ended up having to be exportedin the 2 packages where it ended up copied. And I ran into some weirdness with the events package and a pattern we used already to import from it when aliased as events_pkg to avoid confusion with Node's own events module (import events_pkg from "events_pkg"; const { EventEmitter } = events_pkg;). Importing NodeJS' EventEmitter seems to have worked.

Reviewer Guidance

The review process is outlined on this wiki page.

[alexvy86]

Server code only runs in node, it can use the native performance.now() directly, no need to try to proxy through an isomorphic performance object (which incidentally was already removed in main for the client release group).

[alexvy86]

Not sure if this is really necessary, since it's a @types package. It's there in common-utils.

[alexvy86]

Since the currently exported QuorumClients is built on top of TypedEventEmitter, moving the latter here means that it and all its building blocks need to be exported.

[alexvy86]

Same as in protocol-base; not sure it's necessary. Brought it because it's in common-utils.

[tylerbutler]

I think @ChumpChief and @anthony-murphy have a pretty good idea of what the blockers are for full split of this code. Suggest syncing with them before going too far.

[ChumpChief]

The impression I had was that common-utils was intended to be the set of things that we expected both client/server to use (as opposed to client-utils only being used by the client, for example) and intentionally shared. Is there a particular motivation for splitting it?