Fix vm explorer url

[GilbertCherrie]

Fixes: #6696

Fixes an issue where trying to access URLs related to the VMs:

/vm_or_template/explorer/:id
/vm_cloud/explorer/:id
/vm_infra/explorer/:id

throws an error. This PR fixes this issue and now the page correctly redirects to the correct record.

This PR also fixes the redirect for the storage explorer and catalog explorer with example URLS:

/storage/explorer/:id
/catalog/explorer/:id or /catalog/ot_show/:id (Orchestration templates only, this path already exists on master)

Other explorer fixes:
/miq_ae_class/show/:id (This path already exists on master, this PR just fixes the page)
/miq_ae_customization/editor/:id (This path already exists on master, this PR just fixes the error handling of a bad URL)

Note: The catalog controller only supports the catalog item and orchestration item templates. You can not use raw IDs to direct to service catalogs or catalogs.

Before:

After:

[Fryguy]

What happens if someone passes garbarge, for example /explorer/abc

[GilbertCherrie]

What happens if someone passes garbarge, for example /explorer/abc

@Fryguy it errors out like this

[GilbertCherrie]

@Fryguy I pushed a fix so that bad urls are handled better:

[Fryguy]

A few things -

1. If we want to introduce this in one explorer, let's just introduce them in all of them.
2. The duplication tells me we can extract this to a single method somewhere, use it in a base explorer class, and get it everywhere

[miq-bot]

Checked commits GilbertCherrie/manageiq-ui-classic@791787d~...a1a229c with ruby 3.3.10, rubocop 1.88.2, haml-lint 0.76.0, and yamllint 1.37.1
5 files checked, 2 offenses detected

app/controllers/storage_controller.rb

• ❗ - Line 513, Col 33 - Naming/MethodParameterName - Method parameter must be at least 3 characters long.

app/controllers/vm_common.rb

• ❗ - Line 796, Col 28 - Naming/MethodParameterName - Method parameter must be at least 3 characters long.

[GilbertCherrie]

@Fryguy I fixed the explorers that needed fixing in this PR. The other explorers can't seem to be fixed as they work inherently differently. I asked AI to come up with an explanation on why they can't be fixed and a summary is:

The common thread: the explorers that can be deep-linked (VMs, Storage, Catalog, Automate) share these traits:

A single dominant model type per controller
:full_ids => false trees where node ids are just prefix-id
An existing external trigger (dashboard widget links, exp_parms, cross-controller redirects) that actually generates those URLs
The others have none of those traits — adding deep-link support would require a non-trivial ancestry reconstruction or model disambiguation layer, and there's no external source generating those URLs anyway.