[Dash-Sonic] Introduce route group, pa validation tables

[prsunny]

1. Add Route group table for grouping routes and binding to an ENI
2. Introduce PA validation table for special validation for certain scenarios

[r12f]

do we still need the guid here? @sharmasushant

[prsunny]

guid can be optional

[sharmasushant]

I don't see a use for guid field, but I am okay to leave it there.

[kperumalbfn]

Different ENI ids for group_id_1, group_id_2 and group_id_3.

[prsunny]

This is a reference example. it can be any group_id

[KrisNey-MSFT]

Currently the route table is modified w/routes belonging to an ENI (per ENI).
Controller calls each route update w/ENI key.
Group table & binding allows for atomic binding for an ENI (instead of updating 1 by 1)
(Not a subset of ENI routes).
Cx update their routes in the route table, and expect all or nothing to work. Adding 1 by 1 we can end up in a non-complete/inconsistent goal state.

What if libsai has no resources to support an atomic update?
The controller will need to wait to determine whether this is a successful operation or not.
If unsuccessful, old route table will persist.

[sharmasushant]

LGTM

[KrisNey-MSFT]

Are all comments resolved? IF Y, I can merge :)

[KrisNey-MSFT]

hi @r12f , @kperumalbfn , and @pranjal-git - would you mind reviewing for Prince please?
TY...