Implement new Component class and ObjectPool

[robertlong]

This PR is intended to make the component class more straightforward, predictable, and accessible to tooling.

Object pooling is now handled with .copy() and .clone() methods rather than .reset(). The Component class comes with a default implementation for the constructor, copy, and clone that is based on the component schema.

Components must now be registered, an error will be thrown if you attempt to add a component before it is registered. On component registration we validate the schema. Components must also now extend the Component class.

Schema types have a new interface. They must implement name, default, copy, and clone. Types are validated upon registration.

The createComponentClass helper has been removed. You should now use the Component class instead.

To Do:

• Update docs
  • Remove references to createComponentClass()
  • Update createType() docs
  • Update references to Component .reset()
  • Add new Component docs
  • Add new Entity .copy() and .clone() docs
  • Add ObjectPool docs
• Write more tests
  • Entity .copy()
  • Entity .clone()

Closes #147
Closes #118

[IfnotFr]

Great work with this ! Component schema definition with upcoming proposal-class-fields. Will make some really clear/consice Components :

import { Component, Types } from "ecsy"

class MyComponent {
    static schema = {
        aNumber: { type: Types.Number },
        anArray: { type: Types.Array },
    }
}

[fernandojsg]

@IfnotFr indeed! currently it's a bit uglier but it's fine so far. but when the static will arrive both the Component definition and the System's queries will be prettier for sure :)

[fernandojsg]

I updated the issues regarding the documentation and tests that we should update
#190
#165