disabling flaky test

[agunapal]

Description

Disabling the test test_register_model_with_batch_size since this seems flaky on regression runs on GPU

Passing run

 pytest -v test_model_config.py 
================================================================================== test session starts ===================================================================================
platform linux -- Python 3.10.0, pytest-7.3.1, pluggy-1.0.0 -- /home/ubuntu/anaconda3/envs/ts_aot_compile/bin/python
cachedir: .pytest_cache
rootdir: /home/ubuntu/serve
plugins: cov-4.1.0, mock-3.12.0
collected 2 items                                                                                                                                                                        

test_model_config.py::test_register_model_with_batch_size PASSED                                                                                                                   [ 50%]
test_model_config.py::test_register_model_without_batch_size PASSED      

Failing run

pytest -v test_model_config.py 
================================================================================== test session starts ===================================================================================
platform linux -- Python 3.10.0, pytest-7.3.1, pluggy-1.0.0 -- /home/ubuntu/anaconda3/envs/ts_aot_compile/bin/python
cachedir: .pytest_cache
rootdir: /home/ubuntu/serve
plugins: cov-4.1.0, mock-3.12.0
collected 2 items                                                                                                                                                                        

test_model_config.py::test_register_model_with_batch_size FAILED                                                                                                                   [ 50%]
test_model_config.py::test_register_model_without_batch_size PASSED    

Fixes #(issue)

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• New feature (non-breaking change which adds functionality)
• This change requires a documentation update

Feature/Issue validation/testing

Please describe the Unit or Integration tests that you ran to verify your changes and relevant result summary. Provide instructions so it can be reproduced.
Please also list any relevant details for your test configuration.

• Test A
  Logs for Test A

• Test B
  Logs for Test B

Checklist:

• Did you have fun?
• Have you added tests that prove your fix is effective or that this feature works?
• Has code been commented, particularly in hard-to-understand areas?
• Have you made corresponding changes to the documentation?