scheduler_v2: implement a data structure for storing table status

[liuzix]

What problem does this PR solve?

• To implement a peer-message based scheduler, we need a data structure to store and look up information of all the replicated tables.

What is changed and how it works?

• Implemented TableSet.
• Methods include:

AddTableRecord(record *TableRecord) (successful bool)
GetTableRecord(tableID model.TableID) (*TableRecord, bool)
RemoveTableRecord(tableID model.TableID) bool
RemoveTableRecordByCaptureID(captureID model.CaptureID)
CountTableByCaptureID(captureID model.CaptureID) int
GetDistinctCaptures() []model.CaptureID
GetAllTables() map[model.TableID]*TableRecord
GetAllTablesGroupedByCaptures() map[model.CaptureID]map[model.TableID]*TableRecord
CountTableByStatus(status TableStatus) (count int)

Check List

Tests

• Unit test

Release note

None

[ti-chi-bot]

[REVIEW NOTIFICATION]

This pull request has been approved by:

• 3AceShowHand
• asddongmen

To complete the pull request process, please ask the reviewers in the list to review by filling /cc @reviewer in the comment.
After your PR has acquired the required number of LGTMs, you can assign this pull request to the committer in the list by filling /assign @committer in the comment to help you merge this pull request.

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

Reviewer can indicate their review by submitting an approval review.
Reviewer can cancel approval by submitting a request changes review.

[liuzix]

/run-leak-tests

[overvenus]

Rest LGTM

[3AceShowHand]

LGTM

[asddongmen]

/rest LGTM

[amyangfei]

/merge

[ti-chi-bot]

This pull request has been accepted and is ready to merge.

Commit hash: 4d3f2ac

[liuzix]

/run-integration-tests