refactor current pagination solution using router

[Viterbo]

          @EJSG, thanks for that review! That bug you found was the last drop I needed to push myself to find a better solution. Fortunately, I did.

I changed the strategy from a homemade solution using history.pushState to a more easy and elegant solution using $router (which is intended for these cases).

    async onPaginationChange(props) {
        const { page, rowsPerPage } = props.pagination;
        this.$router.push({
            hash: window.location.hash,
            query: {
                ...this.$route.query,
                page: `${page},${rowsPerPage}`,
            },
        });
    },

watch: {
    '$route.query.page': {
        handler(_pag) {
            let pag = _pag;
            let page = 1;
            let size = this.pagination.rowsPerPage;

            // we also allow to pass a single number as the page number
            if (typeof pag === 'number') {
                page = pag;
            } else if (typeof pag === 'string') {
                // we also allow to pass a string of two numbers: [page, rowsPerPage]
                const [p, s] = pag.split(',');
                page = p;
                size = s;
            }

            this.setPagination(page, size);
        },
        immediate: true,
    },
},

I'm going to create a new issue to implement this same solution on the TransactionTable

Originally posted by @Viterbo in #346 (comment)