Investigate using SpeedyAF for edit page rendering

[masaball]

Description

Currently the edit pages are populated from fedora. We could potentially decrease rendering times if we can leverage SpeedyAF. We will still need to load the fedora object for the actual update and save, but using SpeedyAF for the initial loading and populating of the edit pages could reduce the initial overhead and speed up load times.

As part of this, can/should we rework loading and authorizing the objects? Currently we use a load_and_authorize_resource callback, but this can be somewhat lengthy and may be triggering for each type of resource (fedora object, SpeedyAF proxy, raw solr object, etc) rather than running once.

Done Looks Like

• Use SpeedyAF for populating edit page fields instead of Fedora
• Change object authorization strategy from the current callback to something more performant