Weverse

- The client start method now takes a parameter `create_media` which is set to `False` by default. When set to `True`, it will create all past media.

- If a media post contains photos, the media object will now store those photos. This was an important feature that was missing by lack of research. If you are a user that keeps tracks of notifications, it would be advised to rework your media section if you specifically post photos.

- client.determine_notification_type can now either take the notification body **OR** the notification itself.

- If a weverse account is set to **KOREAN**, the output comes back as korean on the bot. This is fixed by adding korean triggers if the bot still wants the account to be korean. This was also a fix for determining the notification type accurately. It is possible some triggers may be missing, but majority of the Korean and English ones should have been added.

This was an update to prevent new posts being lost in the void.

Since it is possible for several posts to happen at the exact same time, there is now a [method](https://weverse.readthedocs.io/en/latest/api.html#Weverse.WeverseClient.get_new_notifications) that will get **ONLY THE NEW** user notifications **AFTER** the client has checked for new notifications. The example usages can be found below.
[Asynchronous Example](https://github.com/MujyKun/Weverse/blob/a5eb6033a1a754ca9b482ba2b481b6d953921fb3/examples/asynchronous.py#L70)
[Synchronous Example](https://github.com/MujyKun/Weverse/blob/a5eb6033a1a754ca9b482ba2b481b6d953921fb3/examples/synchronous.py#L112)

The examples have been updated and there has been added type-support.

Notifications are also now comparable with the equal operator by differentiating IDs.

Added Proper Type Support for Posts

Added support for videos.

Added more detailed examples.

The start method now contains options for loading cache. This will benefit clients that only care about future objects and not past ones.