CNV-39727: fix pagination on bootablevolume selection

[upalatucci]

📝 Description

When selecting a bootable volume in instancetype VM creation, the list pagination gets on the first page.
This because we are using the unsorted list to calculate in which page we should be.

Why we do that? Because user can select the bootablevolume from a modal clicking on 'Show all' bootable volume. And clicking on 'select' should change the list page into the current selection page.

So we need a sorted array for identify the right page in which the selection is and a sortedPaginated array to show just the paginated volumes that we want in the list

Another fix:

TabModal expect a submit method that return a promise. So just return a promise.resolve instead of changing the type.
Just changing the type result into an infinite button loading in the modal .

[openshift-ci-robot]

@upalatucci: This pull request references CNV-39727 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the bug to target the "4.16.0" version, but no target version was set.

In response to this:

📝 Description

When selecting a bootable volume in instancetype VM creation, the list pagination gets on the first page.
This because we are using the unsorted list to calculate in which page we should be.

Why we do that? Because user can select the bootablevolume from a modal clicking on 'Show all' bootable volume. And clicking on 'select' should change the list page into the current selection page.

So we need a sorted array for identify the right page in which the selection is and a sortedPaginated array to show just the paginated volumes that we want in the list

Another fix:

TabModal expect a submit method that return a promise. So just return a promise.resolve instead of changing the type.
Just changing the type result into an infinite button loading in the modal .

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: metalice, upalatucci

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [metalice,upalatucci]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[upalatucci]

/retest

[metalice]

/retest

[upalatucci]

/retest