zebra: Fix to avoid two Vrfs with same table ids (backport #16350)

[mergify]

During internal testing, when the following sequence is followed, two non default vrfs end up pointing to the same table-id

• Initially vrf201 has table id 1002
• ip link add dev vrf202 type vrf table 1002
• ip link set dev vrf202 up
• ip link set dev master vrf202

This will ideally lead to zebra exit since this is a misconfiguration as expected.

However if we perform a restart frr.service at this point, we end up having two vrfs pointing to same table-id and bad things can happen.

root@mlx-3700-20:mgmt:/var/log/frr# sudo vtysh -c "sh vrf" vrf mgmt id 37 table 1001
vrf vrf201 id 46 table 1002
vrf vrf202 id 59 table 1002 >>>>

Fix: in all cases of misconfiguration, exit zebra as expected.

Ticket :#3970414

---

This is an automatic backport of pull request #16350 done by Mergify.

[mergify]

Cherry-pick of c77e157 has failed:

On branch mergify/bp/stable/9.0/pr-16350
Your branch is up to date with 'origin/stable/9.0'.

You are currently cherry-picking commit c77e15710d.
  (fix conflicts and run "git cherry-pick --continue")
  (use "git cherry-pick --skip" to skip this patch)
  (use "git cherry-pick --abort" to cancel the cherry-pick operation)

Unmerged paths:
  (use "git add <file>..." to mark resolution)
	both modified:   zebra/interface.c

no changes added to commit (use "git add" and/or "git commit -a")

To fix up this pull request, you can check it out locally. See documentation: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/reviewing-changes-in-pull-requests/checking-out-pull-requests-locally