[FRR]Adding patch to fix enhanced capability turned on for interface

[dgsudharsan]

Why I did it

Fixing issue

https://github.com/FRRouting/frr/issues/11108

For interface based peers with peer-groups, "no neighbor capability extended-nexthop" gets added by default. This will result in IPv4 routes not having ipv6 next hops.

How I did it

Porting the commit 8e89adc1edfb4200843e1cbbff1404172bebd9e5 to FRR 8.2.2 which fixes the issue

How to verify it

Load FRR and verify if the "no neighbor capability extended-nexthop" not gets added for interfaces associated with peer-groups

Before fix

show running-config
Building configuration...

Current configuration:
!
frr version 8.2.2
frr defaults traditional
hostname r-lionfish-16
no service integrated-vtysh-config
!
router bgp 65001
 no bgp suppress-duplicates
 neighbor PEER_V6 peer-group
 neighbor PEER_V6 remote-as internal
 neighbor PEER_V6 capability extended-nexthop
 neighbor Ethernet116 interface peer-group PEER_V6
 no neighbor Ethernet116 capability extended-nexthop
 !
 address-family ipv4 unicast
  redistribute connected
 exit-address-family
 !
exit

After fix

show running-config
Building configuration...

Current configuration:
!
frr version 8.2.2
frr defaults traditional
hostname r-lionfish-16
no service integrated-vtysh-config
!
router bgp 65001
 no bgp suppress-duplicates
 neighbor PEER_V6 peer-group
 neighbor PEER_V6 remote-as internal
 neighbor PEER_V6 capability extended-nexthop
 neighbor Ethernet116 interface peer-group PEER_V6
 !
 address-family ipv4 unicast
  redistribute connected
 exit-address-family
 !
exit

Which release branch to backport (provide reason below if selected)

• 201811
• 201911
• 202006
• 202012
• 202106
• 202111
• 202205

Description for the changelog

Ensure to add label/tag for the feature raised. example - PR#2174 under sonic-utilities repo. where, Generic Config and Update feature has been labelled as GCU.

Link to config_db schema for YANG module changes

A picture of a cute animal (not mandatory but encouraged)