[BYOC][oneDNN] Update and maintain oneDNN BYOC integration

## Motivation

The oneDNN BYOC integration in TVM is currently not being actively maintained and is based on an older version of oneDNN.

We would like to actively maintain the oneDNN BYOC integration in TVM and bring it up to date with the current oneDNN implementation. This will help keep the integration compatible with newer oneDNN releases and provide a better foundation for further improvements and testing.

## Initial Scope

As the first step, we would like to:

* Update the oneDNN dependency used by TVM to a recent upstream version.
* Update the existing oneDNN BYOC integration to be compatible with the newer oneDNN APIs.
* Fix any build or API compatibility issues introduced by the version update.
* Ensure the existing oneDNN BYOC functionality continues to work.
* Update/add relevant unit and integration tests as required.

## Future Scope

Once the oneDNN version is updated successfully, we would like to continue maintaining the oneDNN BYOC integration and potentially address:

* Additional operator support.
* Improved operator fusion and pattern support.
* Performance improvements.
* Better test coverage.
* Compatibility with newer oneDNN releases.
* CI coverage for the oneDNN BYOC integration, where appropriate.

## Proposed Tracking Items

* [ ] Update oneDNN dependency to a recent upstream release.
* [ ] Resolve API and build compatibility issues.
* [ ] Validate existing oneDNN BYOC functionality.
* [ ] Update/add tests.
* [ ] Document the supported oneDNN version and integration status.
* [ ] Identify additional maintenance and improvement work.

## Expected Outcome

A maintained and up-to-date oneDNN BYOC integration that is compatible with a recent oneDNN release and provides a stable foundation for continued development within TVM.

We would also be interested in contributing the required changes and helping maintain the oneDNN BYOC integration going forward.

Start by locating TVM's existing oneDNN BYOC integration, its dependency configuration, and the current unit or integration tests. Check the supported oneDNN version and run the existing BYOC validation before updating APIs. Done means the dependency is current, builds succeed, existing functionality still passes, relevant tests and documentation are updated, and remaining maintenance work is identified.

Written by the indexing model from the issue text.