Trace shutdown processing needs to be after other shutdown processing

[bobbingwide]

The trace log that I used when analyzing Automattic/jetpack#3579 showed Jetpack's shutdown processing after oik-bwtrace's. oik-bwtrace should hook into shutdown later than it currently does.

[bobbingwide]

Actually, Jetpack's shutdown processing does occur before oik-bwtrace's, but Yoast's doesn't

/home/oikcouk/public_html/wp-content/plugins/oik-bwtrace/includes/bwtrace-actions.php(410:) bw_trace_attached_hooks(3) 583 2016-03-24T10:12:51+00:00 17.757882 0.005582 cf=shutdown 41 0 47137224/50456496 F=529 shutdown 
: 0   bw_trace_attached_hooks;9
: 1   wp_ob_end_flush_all;1
: 8   Jetpack_Sync::register_all_options;1 Jetpack_Sync::register_all_module_constants;1
: 9   Jetpack_Sync::sync;1
: 10   bw_trace_count_report;1 bw_trace_included_files;1 bw_trace_saved_queries;1 bw_trace_status_report;1 Yoast_Notification_Center::set_transient;1

Note: Jetpack attaches different hooks with different priorities dependent upon the context. See the rather out of date http://jetpack.wp-a2z.org/oik_hook/shutdown/

[bobbingwide]

JetPack's Sync logic has now changed. See bobbingwide/oik-clone#15