Remove unused Hibernate dep from Serving

[ches]

What this PR does / why we need it:

Removes an unused dependency. Just a little housekeeping noticed in the context of something related. Core and Serving were using different versions of Hibernate, which I first wanted to align, then thought to myself, "wait, how does Serving use Hibernate?"

Maybe someone knows the background of what "Hibernate for formatting SQL string" meant, but grepping/mvn dependency:analyze/building suggests it is indeed unused.

Which issue(s) this PR fixes:

No issue

Does this PR introduce a user-facing change?:

NONE

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ches
To complete the pull request process, please assign davidheryanto
You can assign the PR to them by writing /assign @davidheryanto in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[ches]

/assign @davidheryanto

[woop]

Flaky tests are killing me.

[ches]

I tried one rerun of the Docker Compose workflow, still got timeouts. Looks like it's failing on every recent PR.

[woop]

I tried one rerun of the Docker Compose workflow, still got timeouts. Looks like it's failing on every recent PR.

Ah, it's supposed to be failing. Yay. So it's not flakiness, it's due to not updating the SDK to the latest version. Will have a look a bit later.

And documentation is still pending for me.

[davidheryanto]

/lgtm
I think the Hibernate library was used last time to format the SQL query we generate for querying historical storage (i.e BigQuery). But yeah it seems we no longer use it.

[woop]

I tried one rerun of the Docker Compose workflow, still got timeouts. Looks like it's failing on every recent PR.

I believe I have fixed the docker compose test, but for some reason your test isnt using the code that is on the master branch. It should be cloning the v0.5-branch into the docker compose tests.

I think you should maybe just rebase and try again.

Might be smarter to only run these Docker Compose tests on master and not on PRs.

[feast-ci-bot]

New changes are detected. LGTM label has been removed.

[ches]

/retest

Docker Compose Actions workflow still appears to time out.