[FEATURE] Improved Home, Plugins & Ban sections

### What's needed and why?

Hello to you team,

I currently have another security system where I have a list of banned IPs.

I would like to integrate them directly into BunkerWeb but there is no import button. So I’m doing it one by one...

This is why these improvements could solve this problem.

### In the Home section:
- Provide a map of banned IPs by country.

### In the Bans section:
- It is possible to modify one or more line(s) to increase the expiry date, the reason for the BAN as well as the scope
- Import a list of IPs to ban via CSV; (Propose a file to be respected for the import)
- When adding a BAN, propose a button or something like that so the Ban never expires
- When adding a BAN, if you add it via the INSERT button, repeat the expiration date of the previous ban
- When adding a BAN, possibility to ban an IP pool in one go ?

### In a Plugin section (Plugins Pages) :
- Ability to click a change button that redirects us in the Global Config section for the plugin we want to modify.

Thank you for your time.

Good day to you.

### Implementations ideas (optional)

### In the Home section:
-> **Either put another widget next to the Blocked Requests or create another view on the current map.**

### In the Bans section :
- It is possible to modify one or more line(s) to increase the expiry date, the reason for the BAN as well as the scope
-> **Have a modified button and the possibility to modify the values indicated**

- Import a list of IPs to ban via CSV; (Propose a file to be respected for the import)
-> **Add an import button with a sample file with the requested columns.**

### In a Plugin section (Plugins Pages) :
- Ability to click a change button that redirects us in the Global Config section for the plugin we want to modify.
-> **Add an edit button on plugin pages that redirects to the plugin in Global Config.**

### Code of Conduct

- [x] I agree to follow this project's Code of Conduct

Start by locating the Home, Bans, and Plugins pages and their existing ban-management and plugin-configuration entry points; no files or tests are named in the issue. Define the scope with maintainers, then verify each requested interaction, including CSV import, ban editing and expiry behavior, IP-pool bans, the country map, and plugin edit navigation.

Written by the indexing model from the issue text.