Fixes for Ionosonde and rate limiting of console messages when debugging

[alanhargreaves]

What does this PR do?

1. If LOG_LEVEL is 'debug' don't rate-limit log messages - [BUG] fetchIonosondeData() is not mapping station times correctly #722
2. Force the timestamp gathered by fetchIonosondeData() to be interprested as UTC, so those of us more then two hours in front of UTC can get some data - [BUG] Turn off rate limiting when LOG_LEVEL is debug #721

Type of change

• Bug fix
• New feature
• Performance improvement
• Refactor / code cleanup
• Documentation
• Translation
• Map layer plugin

How to test

Ionosonde

1. Be in a timezone more than two hours in front of UTC
2. Enable the MUF layer (hot key 'm')
3. Note that we are now getting ionosondes

Debug messages

1. Set LOG_LEVEL to be debug in .env
2. Restart the server
3. Note that we are now seeing all log messages (e.g. we get a non-clipped logo)

Checklist

• App loads without console errors - Well, actually I guess we get more messages but that is the point
• Tested in Dark, Light, and Retro themes
• Responsive at different screen sizes (desktop + mobile)
• If touching server.js: caches have TTLs and size caps (we serve 2,000+ concurrent users)
• If adding an API route: includes caching and error handling
• If adding a panel: wired into Modern, Classic, and Dockable layouts
• No hardcoded colors — uses CSS variables (var(--accent-cyan), etc.)
• No .bak, .old, console.log debug lines, or test scripts included