add next/image and next-video in next namespace

[Lendemor]

No description provided.

[masenf]

i think we should keep rx.image pointing to the Chakra image for now, but we should get this out there and switch reflex-web over to use it and do some more battle testing.

[masenf]

looks good, the image stuff works and serialization of PIL images is still working.

i'm not sure about next-video, but it doesn't seem to be harming anything here, just not sure if it can actually be used.

[masenf]

what does this component actually do? reading through the docs here https://next-video.dev/docs

it seems like it's a video uploading and hosting service with nextjs integration. i'm not 100% sure this makes sense in reflex, especially not without the associated next.config.js

/** @type {import('next').NextConfig} */
const { withNextVideo } = require('next-video/process');
 
const nextConfig = {}; // Your current Next Config object
 
module.exports = withNextVideo(nextConfig);

I think this could be part of our asset story, particularly with the hosting service which does not have a lot of disk, but it seems to be missing parts and definitely needs documentation.