Review routes and ensure that there are no more navigation warnings around calling next more than once

[javihernandez]

As unveiled in the following issue and resolved in this PR, there might be some navigation in other places due to use of calling next() as part of promise handling in the routing process.

We should review albs-frontend's routes.js and ensure that:

• We stop calling next, and pass it as a callback in the promise resolution process
• Several store/state dispatchers in beforeEnter should be wrapped into a Promise.all

After the update, we need to check that the navigation works as expected and that there are no more navigation warnings around.