Remove the need for the destroy hook in the basic APM case.

This avoids creating a temporary v8::Global

This means the sync executor or sync start of an async function
will have the same execution async resource as the caller
which may result in unexpected behaviour but it is likely better
than hijacking the rest of the sync context with the promise
as the current execution async resource.

The reference must live long enough to be used for async_hooks triggers
but must be reset when a destroy occurs to ensure the resources don't
cause a leak but also don't cause a crash.

…r methods and avoid delete keyword

Add missing parameters to the test file and rename an option
to avoid naming conflicts with another async_hooks benchmark.