Fix new web panel bugs

Login & Register Page

1. Fix the login/register input labels not doing anything on click.
   A fix for this is by changing the "for" attribute of the label. Let it point to the input as intended by HTML standards. Doing this in the following way: for="inputUsername" for the username label. When clicking on the username label now, the typing starts.
2. Add the link to the verification page inside of the mail.
   When they accidentally click away the tab, they can easily go to the verification page by clicking on it inside of the email.
3. Give a prompt or alert when verification has succeeded.
   Instead of just redirecting to the login page. Give the users notice, that their email/account has been verified.
4. Login password can be empty.
   The password input field can be empty, and so it generates an error in the console. Add a check to see if the password is not empty and more than 4 characters long.
5. Incorrect username/email does not give error message.
   An unknown username/email does not always show the error message. It keeps stuck on: "Trying to login your user...". Although the server sends the correct code back: unknown_user_or_email.

Dashboard - Add Servers

1. **Add options to stop and/or go back in the process.
   Adding the button to go back a step, would be very helpful. Also a button that stops the process.
2. People can spam the Next Step button in the second step.
   This is the same for the login page. Maybe add a delay so people do not send enormous amounts of requests. This happens when the login data is wrong.
3. Do not request API password/IP address when a license is already added to the account.
   When clicking on the Add Servers button, it requests their data everytime. Do not do this when a license it already attached, just skip immediately to step 3.

Dashboard - Watch Server

1. Do not update blacklist/whitelist graphs every 3 seconds.
   The plugin only sends the blacklist/whitelist data every 5 minutes. No need of updating the graphs every 3 seconds.
2. Set the tag column to null if the custom tag is empty.
   Instead of setting the IP as tag, make it null. If a change in format is needed later, this helps better. It also makes sure "Write a name" is visible in the custom tag input field.
3. Add possibility to remove a server from the panel.
   If an IP is not used anymore, give the option to remove the IP from the panel. This does not remove the license.
4. Add option to reorder the servers
   Users should be able to reorder their servers. Although there is currently no way of doing this within the database. This is not necessary. If you want to do it. Maybe add a column in the web accounts table, and add a column which has a JSON: ["123.123.123.123:456","22.56.78.90"] and this will define the order of IPs.

Small Things

1. Add a BETA tag in the logo
   Just add BETA inside of the logo in the top left, so people know this is still not final.
2. Redirect /BotSentry/panel to /BotSentry/panel/login.
   Instead of throwing an error redirect people from https://cyberdevelopment.es/BotSentry/panel to the login page.
   Maybe also redirect people from https://cyberdevelopment.es/BotSentry
3. Show a dialog/alert when people click "Upgrade to BotSentryPlus"
   Provide information about what BotSentryPlus is going to be, and tell the users that it is still in development.

Language Corrections

1. Trying to login your user... (Login Page)
   The word login is used as a noun, for defining the process. While the actual verb is: "log in". With a space. In this case it should be: "Trying to log in your user..."
2. You must fill the captcha to register. (Register Page)
   The word fill needs the "in" preposition. You fill something in. In this case it should be: "You must fill in the captcha to register."
3. You must fill the captcha to login. (Login Page)
   The word fill needs the "in" preposition. You fill something in. The word login is used as a noun, for defining the process. While the actual verb is: "log in". With a space. In this case it should be: "You must fill in the captcha to log in."
4. Comma and point use (Dashboard - Global BotSentry Stats)
   In English the . is used as decimal pointer. The PREVENTED BOTS (LIFETIME) should have comma's.
5. Bot-Sentry (Dashboard - Global BotSentry Stats)
   Remove the dash: "BotSentry" in Blacklisted IPs Graph, Whitelisted IPs Graph, Requests Graph
6. Top 10... coming from detected through all BotSentry servers (Dashboard - Global BotSentry Stats)
   "coming from detected through all BotSentry servers" sounds very very odd. A better way of saying this: "Top 10 X with most bots, detected by all BotSentry users."
7. received through (Dashboard - Global BotSentry Stats)
   "received through" sounds odd. Prefer using: "received by". In the graph of: Daily attacks.
8. /botsentry apipassword (password) (Dashboard - Add Servers)
   Use Minecraft command display system: "" with <> instead of ().
9. write it in the field above (Dashboard - Add Servers)
   Should be in the field "below". The field is below the message.
10. You need to fill all the information (Dashboard - Add Servers)
    The word fill needs the "in" preposition. You fill something in. In this case it should be: "You need to fill in all the information."
11. You will see them now on the side-bar. (Dashboard - Add Servers)
    Different word order. Time can only be in specific places. In othis case: "You will now see them on the side-bar."
12. Maybe full word: Statistics
    In the whole dashboard. In some places there is enough space to type Stats fully: Statistics.

Start by reviewing the Login & Register Page, Dashboard - Add Servers, Dashboard - Watch Server, /BotSentry/panel, and /BotSentry routes named in the issue. Separate the requested fixes, features, redirects, and wording changes into scoped tasks; done means each selected behavior and language correction is implemented and verified without leaving the listed regressions.