issue: 1214066 Update some unsigned char -> uint32_t for table_id

[jdrouhard]

Description

This fixes a few places that weren't updated from unsigned char to uint32_t when support for extended route and rule tables was done for issue 1214066 (a90d08dd5140e0cbc6b6a45ddf71ebda69bb4141)

What

Changes type for table_id from unsigned char -> uint32_t in more places.

Why ?

Extended routing table IDs overflow when used in these functions since unsigned char can only contain values up to 255 (8 bits) but extended table IDs can be 32 bits.

Change type

What kind of change does this PR introduce?

• [X] Bugfix
• [ ] Feature
• [ ] Code style update
• [ ] Refactoring (no functional changes, no api changes)
• [ ] Build related changes
• [ ] CI related changes
• [ ] Documentation content changes
• [ ] Tests
• [ ] Other

Check list

• [ ] Code follows the style de facto guidelines of this project
• [ ] Comments have been inserted in hard to understand places
• [ ] Documentation has been updated (if necessary)
• [ ] Test has been added (if possible)

[swx-jenkins3]

Can one of the admins verify this patch?

[jdrouhard]

Should I change the merge target to the 9.0_LTS branch? this bug actually hit us earlier this week when we set up some routing table policies.

[jdrouhard]

Ping @igor-ivanov @iftahl - not sure exactly how PRs in this repo get merged or how issues are tracked, but I just want to bring attention to this. This bug is causing us to not be able to use VMA since we rely on some policy based routing using extended table IDs which doesn't currently work without this bug fix.

[igor-ivanov]

@jdrouhard please update commit message using format as "issue: 1214066 Update ..."

[igor-ivanov]

bot:retest

[AlexanderGrissik]

bot:retest

[AlexanderGrissik]

bot:retest

[AlexanderGrissik]

bot:retest