Added light theme on HivePulse app and other improvements

One of the feedback on the Hive Pulse app was that it only had a dark theme. And that is quite true as even behind the hood there was also a light theme, I didn't like the look and feel for it so I decided to disable it until I got it right. And today I took the time and reviewed all the pages and controls, did some tweaks and I think I got to a result that I can push to Production. So that's what I did and users can now pick between dark and light themes, while I have kept the default as dark as I like it more and it is better for my eyes. And besides this other improvements were pushed as well in terms of app performance and responsiveness alongside some functionality fixes.

Theme configuration

The end user can now configure which theme they want to use for the Hive Pulse app. The options are:

• 'dark' — dark theme, default
• 'light' — light theme, configurable

Hive API nodes rotation

In the UI node rotation toggle + frontend rotation, I've added a "Node rotation" toggle (default: on) in the Config/All Nodes section before Ping All. New node rotation functionality invokes Hive API on timeout/network errors and tries other nodes automatically. If a fallback node succeeds, the active node in the store is updated to it. Applied to all the pages and this is stored locally to be used for future API calls.

History operations

New operations where not mapped in the History section and their presentation was different than formal components. In order to increase usability and ensure a consistent display of Hive operations, I have formatted new components for them (for example Delegate HP related ops).

Optimized refresh actions

The app is built up in order to perform an initial sync aggregation from the Hive blockchain and afterwards to simply perform incremental requests just to fill the new data. This ensures less Hive API calls which is better for the performance of the app and also not to overcrowd the blockchain with useless requests. Some of the incremental requests where optimized when it comes to the interval at which they kick in for the auto-refresh functionalities.

Some of the above new implementations (light theme) came from community feedback, while others are more technical and implied mostly changes to improve usability and performance. I still have some new bigger features in my mind that I want to lay down and start implementing, so I hope to approach that closer to the weekend. But there is still progress and it gives me motivation to keep on going and be creative and think of other implementations. Of course I am considering also incoming feedback from the community, so that's another dimension for future changes. I know I might move like a turtle and not a rabbit, but the turtle won the race at the end. So one step at a time, but the app I think is shaping pretty good based on my standards.