Replace chrome-aws-lambda with @sparticuz/chromium because of lacking node 16 support

[bastiW]

There seem to be some issues with node 16. So people are downgrading to node version 14. (e. g. here #35 (comment))

So I would suggest moving away from chrome-aws-lambda and using @sparticuz/chromium instead. This lib is more up-to-date and it looks like it supports node 16.

[bastiW]

I have tested it with @sparticuz/chromium

See this commit in my local repository.

6d922b8

When I use it within the ./example directory everything works 😃

[bastiW]

Unfortunately when I deploy it to vercel I get the following error:

2022-12-06T20:57:33.992Z	a679715f-e69b-4abe-8d70-f5c1cf49e755	ERROR	[Error: ENOENT: no such file or directory, open '/var/task/node_modules/@sparticuz/chromium/bin/chromium.br'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/var/task/node_modules/@sparticuz/chromium/bin/chromium.br'
}
2022-12-06T20:57:33.992Z	a679715f-e69b-4abe-8d70-f5c1cf49e755	ERROR	[Error: ENOENT: no such file or directory, open '/var/task/node_modules/@sparticuz/chromium/bin/chromium.br'] {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/var/task/node_modules/@sparticuz/chromium/bin/chromium.br'
}
RequestId: a679715f-e69b-4abe-8d70-f5c1cf49e755 Error: Runtime exited with error: exit status 1
Runtime.ExitError

For testing I have published a fork to the following npm repository:
https://www.npmjs.com/package/next-api-og-image-sparticuz