[Pagination]: Option to generate <a> instead of <button>

[Youhan]

Description

The <UPagination generates <button> elements and attaches an on-click event handler to update the page v-model.
One shortcoming with the is that when you nuxt generate, the Nitro crawler does not see the pagination links and can't follow them, leading to only the first page being generated (or at least that's my understanding). I think that would be same issue with Google bots not being able to identify pagination links.

The feature I am requesting is to add a prop or a few props that work together to add the functionality to generate <a>s instead of <button>s with corresponding pathname or query params.

Now, there are 2 ways I can think someone would implement pagination in the URL.

1. query params: /category/catname?page=4
2. pathname: /category/catname/4

Thought?

Additional context

No response

[Youhan]

I think it would be nice to migrate from <button to <a for all cases but the <UButton would need the correct href (or to)

[Youhan]

Possible solution could be to expose a slot with props to give control to the user on how they want to render the links.

[hddhyq]

@benjamincanac I noticed that UButton supports the link mode by default. I want to create a PR for this issue to add more properties support for UButton in Pagination. Like doing it as follows:

<UPagination 
  v-model="page" 
  :page-count="5" 
  :total="items.length" 
  :link="{
    to: (page) => `/category/catname?page=${page}`
    _target="_self"
  }" />