Add a HOF for wrapping getServerSideProps handlers

[haydn]

• Add withAxiomNextServerSidePropsHandler
• Export all withAxiom functions
• Change type signature for withAxiomNextApiHandler
• Change type signature for withAxiom

[vercel]

@haydn is attempting to deploy a commit to the AxiomFM Team on Vercel.

A member of the Team first needs to authorize it.

[haydn]

I still need to do a bit of testing and update the README before that marking this ready for review. Also, the changes to the type signatures might be considered a breaking change — would it better to keep that out of this PR?

[schehata]

hey @haydn thanks for your contribution! I will take a look right now.

[schehata]

all looks good, can you add an example for usage in the examples folder?

Maybe we can add this to the README:

## getServerSideProps

To be able to use next-axiom with `getServerSideProps` you need to wrap your function with `withAxiomGetServerSideProps`, becasue there is no
way at the moment to automatically detected if getServerSideProps is used.

```ts
import { withAxiomGetServerSideProps } from 'next-axiom'
export const getServerSideProps = withAxiomGetServerSideProps(async ({ req, log })  => {
  log.info('Hello, world!');
  return {
    props: {
    },
  }
});

[schehata]

oh I remembered one more thing, we will need to export the new types in src/index.ts so that the types would be available for next-axiom users.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated
next-axiom-example	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Jan 27, 2023 at 10:08AM (UTC)

[schehata]

I made some changes, but I wasn't able to write a good test for this, as I am not able to use expect against type AxiomGetServierSideProps. any ideas to improve this? @bahlo @haydn