expanding api & adding tokens

[PotentialStyx]

so currently the limited repldex api doesn't have any tokens, and no way to ratelimit, or have restricted access, i suggest that using mongo db to store a token and there permissions, the permissions would be a list with all the permissions, and it would also store meta data in other properties, use as a ratelimit, or if it's request use a cache or not. These could also be controlled thru the admin panel.

checklist:

• api docs
• serve api docs on site
• add tokens
• store tokens in db
• token permissions
• ratelimit's (maybe)
• more api paths (edit, create entries)
• api caching
• non token paths
• easy permissions extendability
• admin panel for tokens

[mat-1]

Imo ratelimits aren't really necessary since not much is being done on the backend when it's used, tokens are annoying, and people could just scrape if they want to bypass the ratelimits anyways.

[PotentialStyx]

Maybe if you don't use a token you get standard access, but using (and getting a token with privilege) can let you do privlaged things like edit, unlist, delete (when added), and modify editors

[PotentialStyx]

Tho highly privlaged tokens (ones with admin features will prob never be given out)

[PotentialStyx]

@JetStream0 doing this here mat1/ReplDex#api-dev

[PotentialStyx]

Checklist in #45

[PotentialStyx]

Closed #45 becuase it is outdated

[selectdev]

We might add this into v3, not too sure yet.