Don't send meta events during replication.

The application state already includes the application's response to
member changes. It shouldn't receive the events again as the state is
restored.
Move common css between index and 404 redirect pages into css file. Refs #4061.
Add pointer event definitions to the yaml file, now required to obtain pick info. Fixes #4050.

Additionally, remove initializeCamera function and clean up minor space issues.
Support `devicePixelRatio` !== 1. Fixes resize issues on Retina displays.
Merge pull request #403 from virtual-world-framework/branch/collection-events-replication

Don't send meta events during replication.
Track method changes in the kernel registry.

References #1662.
Replace `jQuery.each` with `Object.keys` to remove dependency on jQuery.
Only call `model.callingMethod` until the first driver returns a result.
Remove the unneeded `methodValue` parameter from `model.callingMethod`.
Define `kernel.setMethod` and `kernel.getMethod`.
New utility functions to convert between Handlers and functions.
Implement `settingMethod`/ `gettingMethod`; send changes through the kernel.

Conflicts:
	support/client/lib/vwf/utility.js
Replicate method changes.
Detect spacing to retain round-trip formatting in most cases.
Kernel functions shouldn't be called as methods on the driver.
Support keyed and indexed collections in preparation for listener tracking.

- Add `indexedCollectionPrototype` as a parallel to
  `nodeCollectionPrototype` for tracking event listeners and other
  ordered, id-based members. (Should for `node.children` in the future.)

 - Rename `nodeCollectionPrototype` to `keyedCollectionPrototype`.

 - Accept values for the collection `existing` members to be used for
   kernel-authoritative data about the member, such as event parameters
   and listener ids.

- Collect the added/removed/changed bits into one object per collection
  and allow for detailed change state. The detail will include listener
  changes within events.

- Support ordered change lists for indexed collections so that patches
  may apply members added in the necessary order.
Record creations and deletions in the registry.

- Include "added" and "changed" members in the patch data. Previously
  creations were as changes, like any other change.

- The replication data still can't indicate deletions.
Make the registry `collection.existing` objects enumerable.

The `nodes.existing[id].{properties,methods,events}.existing` fields are
created using `Object.create` descriptors, but they weren't setting the
`enumerable` flag. Define new utility functions to build common
`Object.defineProperty` descriptors, and use them in place of the
literal descriptor objects.
Propagate registry collection changes to parent collections.
Support recording events in the node registry.