This object is not needed on Netlify. It is a relict of next-aws-lambda.

When a page is being SSR-ed by a Netlify Function, allow users to access
the function's event and context parameters. These can be accessed as
a property on the `req` object in all SSR-ed pages and in API routes:
- req.netlifyFunction.event
- req.netlifyFunction.context

This allows users to access/leverage Netlify identity for their Next.js
page.
See: #20

It also allows users to modify the callbackWaitsForEmptyEventLoop
behavior.
See: #66 (comment))

Test that users can modify the Netlify Function's
callbackWaitsForEmptyEventLoop behavior via the newly exposed function
event and context objects. When callbackWaitsForEmptyEventLoop is true
(default), the function does not finish until all async processes and
timeouts are completed (or cleared). The user can set this to false to
not wait for other processes to finish.

Add instructions, details, and an example for using Netlify Identity 
with next-on-netlify.

Expose event and context of Netlify Function in Next.js pages and API
routes as `netlifyFunctionParams` (rather than `netlifyFunction`).
The new name is clearer, since we're just making the parameters of the
function available and not the function itself.