Fix pick issue with Degenerate Hexes.

[biagas]

Description

Resolves #19645
Added vtkVisItUtility::EvaluatePosition, which has a fallback for degenerate cells when vtkCell::EvaluatePosition fails.
Updated calls to vtkCell::EvaluatePosition to use the new method where necessary.
Fixed a bit of logic using integer division when it should have been double. It was causing picks to bog down and take quite awhile to return results. 45 seconds for a pick now down to 0.006 in testing.

Type of change

• Bug fix~~
• New feature~~
• Documentation update~~
• Other~~

How Has This Been Tested?

Reminders:

• Please follow the style guidelines of this project.
• Please perform a self-review of your code before submitting a PR and asking others to review it.
• Please assign reviewers (see VisIt's PR procedures for more information).

Checklist:

• I have commented my code where applicable.~~
• I have updated the release notes.~~
• I have made corresponding changes to the documentation.~~
• I have added debugging support to my changes.~~
• I have added tests that prove my fix is effective or that my feature works.~~
• I have confirmed new and existing unit tests pass locally with my changes.~~
• I have added new baselines for any new tests to the repo.~~
• I have NOT made any changes to protocol or public interfaces in an RC branch.~~

[markcmiller86]

I think this explains why I was seeing very long query times in the queries I added to test degenerate hex logic in #20364. I noticed the new queries I added took ~5 mins and should have taken only a second.

Thanks for fixing 💪.

[biagas]

I think this explains why I was seeing very long query times in the queries I added to test degenerate hex logic in #20364. I noticed the new queries I added took ~5 mins and should have taken only a second.

Thanks for fixing 💪.

Am I missing something? I am only seeing a Volume query in your PR, I don't see how my changes would affect the speed of that query.

[markcmiller86]

Am I missing something? I am only seeing a Volume query in your PR, I don't see how my changes would affect the speed of that query.

Hmm...no...maybe I am missing something 😉. But, now that we're clear about the differences, perhaps it is worth a look at those queries too as they take way too long given what I know about what it should really take.