* Prepare for Job events
* Prepare to replace hard-coded Workflow and Job events with more generic events, implemented the event system itself (instead of in the job and worklow systems)

Events:
* Simplified IEventData, removing Key generic parameter
* Renamed eAuditType.eSceneQCd to eAuditType.ePubSceneQCd, to match naming conventions elsewhere
* Initial, WIP versions of EventConsumerJob and EventConsumerWF
* Added eJob and eWF eEventTopic's
* Added eJob* and eWF* eEventKey's
* Modified IEventEngine, replacing createConsumer() with registerConsumer() and unregisterConsumer()
* Modified EventEngine, making it clear that we create a set of system consumers, one per event topic, and then register those via registerConsumer()

* Create a default event producer; expose it's send() method as a method of IEventEngine; this allows event publication without creation of an EventProducer.
* Add eWFGenerateSceneDownloads event key
* Remove IEventConsumer.poll, which was unused, and unnessarily complex

Jobs:
* Record Cook "step" during polling. When it changes from our previously recorded "Step", send an eJobUpdated event
* Replace JobPackrat.updateEngines() with new sendEvent(), using events to inform the WorkflowEngine and JobEngine of job status changes
* Replaced IJobEngine.jobCompleted by making the JobEngine an EventConsumer for Job events.  Use terminating statuses (done, error, cancelled) to clean up the job map

Workflows:
* Replace IWorkflowEngine.jobUpdated(), .event(), and .generateSceneDownloads() with actions initiated by job events.
* Transform WorkflowEngine into a Job and Workflow Event consumer

Cache & Data:
* Removed vocabulary set and vocabulary for eWorkflowEvent

Collections:
* Use events to initiate scene download generation, instead of direct calls to the workflow engine

GraphQL:
* Use events to send the workflow ingest object notification

Storage:
* Use events to send the workflow ingest object notification from AssetStorageAdapter

DBAPI:
* Add "Step" field to JobRun, indicating the current step of a running job as received from Cook

* Used `npx madge --circular --extensions ts ./` to identfy circular dependencies in our code
* Eliminated these through a combination of:
- Using interfaces, where possible
- Extracting selected code into separate files, which could then be imported directly without introducing the circ. dep.
- Use forward declarations

N.B. regressions tests are failing!

* Split part of OCFLObject into OCFLObjectBase, allowing OCFLInventory to access those parts of OCFLObject when OCFLObject needs OCFLInventory ... all without a circular dependency. Yay!

* Avoid attempting to create a system consumer of Job and Workflow events -- there is no system consumer for these!

* Extract from ObjectGraphDatabase those methods needed by ObjectGraph, in order to avoid a circular dependency between ObjectGraph and ObjectGraphDatabase

* Replace partial class definitions with base classes to avoid circular dependencies:
* Move EdanCollection.computeLicenseInfo to PublishScene.computeLicenseInfo
* Declare EventEngine.receive in EventEngineBase abstract class
* Move Downloader.httpRoute to RouteBuilder.httpRoute
* Import SitemapGenerator's real definition in download.ts
* Declare JobEngine.sendJobEvent in JobEngineBase abstract class

* Cache test does not need to use or test DBConnection.disconnect()!
* Address new compilation issues (?)

* For now, disable jest globalTeardown's call to prisma.$disconnect().

* Move Downloader.httpRoute to RouteBuilder.httpRoute