Retrieve the correct cached model batch size in Neuron config checker for Neuron Backend

[jimburtoft]

The Neuron config checker will look at each of the cached models to find any that meet the specified criteria. Specifically, they will DROP for anything with:
Any tp_degree greater than specified:

text-generation-inference/backends/neuron/server/text_generation_server/tgi_env.py

Line 167 in 24c2bff

if neuron_config_dict["tp_degree"] > available_cores:

(leaving anything < or =)

A batch size LESS THAN what was specified:

text-generation-inference/backends/neuron/server/text_generation_server/tgi_env.py

Line 185 in 24c2bff

if batch_size is not None and neuron_config_dict["batch_size"] < int(batch_size):

(leaving anything > or =)

It then sorts anything that that isn't dropped LARGEST to smallest (on both batch size and tp):

text-generation-inference/backends/neuron/server/text_generation_server/tgi_env.py

Line 115 in 24c2bff

return -dictionary["tp_degree"], -dictionary["batch_size"]

Then, it selects the top one on the list to use:

text-generation-inference/backends/neuron/server/text_generation_server/tgi_env.py

Line 153 in 24c2bff

entry = all_compatible[0]

This works great for tp_degree, where you (probably) don't want to run a tp=2 model on a system with 8 cores. But if you specify a batch size of 4, you probably want a batch size of 4, not one of 8.

What does this PR do?

It changes the sort order for batch size so that the smallest valid batch will be first. Since we are looking for something not <, the SMALLEST thing on that list is >= .

No new tests because it should be covered by existing tests.

Fixes # (issue)
Fixing #3299

Before submitting

• This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• [x ] Did you read the contributor guideline,
  Pull Request section?
• [ x] Was this discussed/approved via a Github issue or the forum? Please add a link
  to it if that's the case.
• Did you make sure to update the documentation with your changes? Here are the
  documentation guidelines, and
  here are tips on formatting docstrings.
• Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.