fix: Fix build and check packages flow

[tharapalanivel]

Description of the change

Updating build-and-inspect-python-package to resolve the following issue

× Failed to build `pydantic-core==2.27.2`
  ├─▶ The build backend returned an error
  ╰─▶ Call to `maturin.build_wheel` failed (exit status: 1)

      [stdout]
      Running `maturin pep517 build-wheel -i
      /tmp/baipp-uv_cache_dir/builds-v0/.tmp3oneFf/bin/python --compatibility
      off`
...
        error: the configured Python interpreter version (3.14) is newer than
      PyO3's maximum supported version (3.13)
        = help: please check if an updated version of PyO3 is available.
      Current version: 0.22.6
        = help: set PYO3_USE_ABI3_FORWARD_COMPATIBILITY=1 to suppress this
      check and build anyway using the stable ABI
      warning: build failed, waiting for other jobs to finish...
      💥 maturin failed
        Caused by: Failed to build a native library through cargo
        Caused by: Cargo build finished with "exit status:
      101": `env -u CARGO PYO3_BUILD_EXTENSION_MODULE="1"
      PYO3_ENVIRONMENT_SIGNATURE="cpython-3.14-64bit"
      PYO3_PYTHON="/tmp/baipp-uv_cache_dir/builds-v0/.tmp3oneFf/bin/python"
      PYTHON_SYS_EXECUTABLE="/tmp/baipp-uv_cache_dir/builds-v0/.tmp3oneFf/bin/python"
      "cargo" "rustc" "--features" "pyo3/extension-module"
      "--message-format" "json-render-diagnostics" "--manifest-path"
      "/tmp/baipp-uv_cache_dir/sdists-v9/pypi/pydantic-core/2.27.2/Q8OObY1Vu2MYYSlEhlA5B/src/Cargo.toml"
      "--release" "--lib" "--crate-type" "cdylib"`
      Error: command ['maturin', 'pep517', 'build-wheel', '-i',
      '/tmp/baipp-uv_cache_dir/builds-v0/.tmp3oneFf/bin/python',
      '--compatibility', 'off'] returned non-zero exit status 1

      hint: This usually indicates a problem with the package or the build
      environment.

Related issues or PRs

How to verify the PR

Was the PR tested

Changes were tested by creating a dummy PR to confirm workflow succeeded

• I have added >=1 unit test(s) for every new method I have added (if that coverage is difficult, please briefly explain the reason)
• I have ensured all unit tests pass

Checklist for passing CI/CD:

• All commits are signed showing "Signed-off-by: Name <email@domain.com>" with git commit -signoff or equivalent
• PR title and commit messages adhere to Conventional Commits
• Contribution is formatted with tox -e fix
• Contribution passes linting with tox -e lint
• Contribution passes spellcheck with tox -e spellcheck
• Contribution passes all unit tests with tox -e unit

Note: CI/CD performs unit tests on multiple versions of Python from a fresh install. There may be differences with your local environment and the test environment.