Feed/queue improvements

Along with pagination (which already has a feature request) I'd like to see the following features added to the feed/queue views.

1. Some level of feed filtering. Especially by date as trying to scroll through thousands of images to get back to older generations is a nightmare, not to mention terribly inefficient for your servers to be serving thousands of images as the user scrolls. Being able show just images older than x weeks/months would be good. You could also filter by checkpoint used, posted vs unposted, and/or mature or not.

2. An indicator on images in the feed that have been posted. Currently if I want to post more than 20 images I have to do it over multiple posts, which means remembering which have already been posted as I jump back and forth between feed and post creation. It is easy to double post images when doing this. An icon in the feed showing that the image has already been posted would ease this issue. It could also be used in the filtering in point 1 to filter out posted vs unposted images.

3. Increase the number of images allowed per post if all images in the post were made on site. Since these images are already stored by CivitAI, it makes little sense to restrict them to only 20. Obviously you want to limit users uploading huge numbers of images from off site for storage reasons, but for images made on site having a higher limit would be great. Even just upping it to 50 would be good.

4. Show seed for all generations. Currently if I generate a batch of images using a random seed, the seed field in the generation data shown in the queue is empty. This should include the seed for that image. Currently if I want to know the seed for an image generated in a random batch I have to download it and manually read it's metadata, which is not great UX.

5. Normalise how Remix uses seed. Remix currently works in two ways. In some cases, such as clicking Remix on another users image when the image is being viewed, it'll load the generation data with the seed used for the original image. In other cases, such as when clicking Remix from the hamburger menu on one of my own images in the queue/feed, the seed is empty and you must instead use Remix with seed. In my opinion it would be clearer if Remix always did the same thing. Honestly I'm not even sure why Remix vs Remix with seed is a thing. Why not always have the original seed set, and if the user wants to change it they can?

I have quite a few other ideas for changes but I think this is probably enough for now.

Happy to discuss these in more detail if required. I'm a professional web dev so understand that there may be good reasons why things work as they do that I haven't considered, but these are the changes I'd make if given the chance.