fix: Error handling on nav search for new UI

[tuliomir]

When the user tries to use the search box with the new UI and inputs invalid data ( ex.: an address from another network ), the app throws a javascript error that the ref does not exist.

This was solved by providing an error handler for the Navigation element, with the same fixed positioning as the current UI. Screenshots below for reference.

Acceptance Criteria

• The correct error message is shown when the search box has invalid content

Warning

The PR indicates there are hundreds of changed lines. This happened because I needed to add one indentation to the Navigation file. To avoid confusion on the review proccess, I recommend activating the Hide Whitespaces feature on the files tab.
That way only the actual changes are displayed, and not the hundreds of indentation changes.

Screenshots

New UI

Current UI

Security Checklist

• Make sure you do not include new dependencies in the project unless strictly necessary and do not include dev-dependencies as production ones. More dependencies increase the possibility of one of them being hijacked and affecting us.