Break up queries for point in time correctness joins

[zhilingc]

Plus some gentle refactoring.
The flow for batch retrieval now looks something like this:

            +-------------+
            | load entity |
            | table to    |
            | BQ          |
            +------+------+
                   |
                   |
            +------v-------+
            | Add UUIDs to |
            | entity table |
            +------+-------+
                   |
        +----------+-----------+
        |                      |
+-------v-------+      +-------v-------+
| Point-in-time |      | Point-in-time |
| correctness   | ...  | correctness   |
| join for FS1  |      | join for FSn  |
+-------+-------+      +-------+-------+
        |                      |
        +----------+-----------+
                   |
                   |
            +------v-------+
            | Left join all|
            | subtables to |
            | entity table |
            +------+-------+
                   |
           +-------v--------+
           | output to file |
           +----------------+

All in all this should result in less resource utilisation and faster queries, since we hold less data in memory.

Also to note: at each feature set p-i-t join step, only the relevant entities are used. This allows users to pass in unpartitionable values (like floats) in their entity table as long as they do not use it as an actual key.

[zhilingc]

/retest

[feast-ci-bot]

@zhilingc: you cannot LGTM your own PR.

In response to this:

/lgtm

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[woop]

/lgtm

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhilingc

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zhilingc]

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

[feast-ci-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: zhilingc

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [zhilingc]

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

[zhilingc]

/retest

[davidheryanto]

/lgtm