fix: resolve get entity value for date columns that are related

[jordansoltman]

Closes: #8026

Description of change

Allows for date columns that are part of a relation to have data inserted into them.

Fixes: #8026

Pull-Request Checklist

• Code is up-to-date with the master branch
• npm run lint passes with this change
• npm run test passes with this change
• This pull request links relevant issues as Fixes #0000
• There are new or updated unit tests validating the change
• Documentation has been updated to reflect this change N/A
• The new commits follow conventions explained in CONTRIBUTING.md

[imnotjames]

This needs a test to confirm the behavior

[jordansoltman]

@imnotjames I added a test. Will it be an issue that my last commit message is a merge?

[imnotjames]

No, it's all gravy. We'll probably squash it.

[imnotjames]

We dealt with something similar in #7774 - where only plain objects were treated with this.

Possibly tangentially related kinds of issues.

I'll try to get to actually reviewing this sooner rather than later.

[imnotjames]

This is fine for now. We probably want to make this more general in the future but I think it'll help your exact issue.

In particular, we should really be checking the metadata to confirm that this property is either a plain object or a registered embedded type & failing otherwise.

[jordansoltman]

It does feel like a bandage on a larger issue but I'm very new to TypeORM so I haven't had the time to really understand what the proper fix looks like.

If I stick with TypeORM for future work I'll be happy to circle back and submit a better patch in the future.