<!--
Please make sure you've read and understood our contributing guidelines;
https://github.com/sonic-net/SONiC/blob/gh-pages/CONTRIBUTING.md

Please provide following information to help code review process a bit easier:
-->
### Description of PR
Change custom message name to be more intuitive and set new standard for future message names.
<!--
- Please include a summary of the change and which issue is fixed.
- Please also include relevant motivation and context. Where should reviewer start? background context?
- List any dependencies that are required for this change.
-->

Summary:
Currently, custom message is used to record of failures throughout the test runs. But with names we have now, it might not intuitive enough to understand what the message is about.

Therefore, set new standard for custom message name to be more intuitive and easier to understand, so future custom messages can follow the same standard.

Instead of mixture of xxx_failed and yyy_pass, merge all messages with xxx_failed, so everytime custom message is recorded, it's always result of failures.

### Type of change

<!--
- Fill x for your type of change.
- e.g.
- [x] Bug fix
-->

- [ ] Bug fix
- [ ] Testbed and Framework(new/improvement)
- [ ] New Test case
 - [ ] Skipped for non-supported platforms
- [ ] Test case improvement

### Back port request
- [ ] 202012
- [ ] 202205
- [ ] 202305
- [ ] 202311
- [ ] 202405
- [ ] 202411

### Approach
#### What is the motivation for this PR?
Not intuitive names for custom message.

#### How did you do it?
Change name of custom message names and merge into xxx_failed

#### How did you verify/test it?

#### Any platform specific information?

#### Supported testbed topology if it's a new test case?

### Documentation
<!--
(If it's a new feature, new test case)
Did you update documentation/Wiki relevant to your implementation?
Link to the wiki page?
-->

…ically (sonic-net#14739)

#### Why I did it
src/sonic-dbsyncd
```
* d6b2000 - (HEAD -> 202012, origin/202012) Fix the LLDP_LOC_CHASSIS not getting populated if no remote neighbors are present (sonic-net#39) (sonic-net#58) (7 months ago) [abdosi]
* 0f8d503 - Use github code scanning instead of LGTM (sonic-net#55) (8 months ago) [Liu Shilong]
```

…e latest HEAD automatically (sonic-net#15016)

src/wpasupplicant/sonic-wpa-supplicant

* a24412c25 - (HEAD -> 202205, origin/master, origin/HEAD, origin/202211, origin/202205, master) [mka]: Fix unexpected cleanup (sonic-net#73) (8 days ago) [Ze Gan]
* 26d1da0bc - [mka]: Fix re-establishment by reset MI (sonic-net#72) (8 days ago) [Ze Gan]
* f07e0a097 - [azp]: Update build pipeline to build for Bullseye (sonic-net#70) (4 weeks ago) [Ze Gan]
*   2c69e2cda - Use github code scanning instead of LGTM (sonic-net#69) (6 months ago) [Liu Shilong]
|\  
| * 23abb04e5 - fix (6 months ago) [shilongliu]
| * f34d68fe6 - libdbus-1-dev (6 months ago) [shilongliu]
| * dc2dd881e - add dbus (6 months ago) [shilongliu]
| * 5de037661 - use swsscommon packages (6 months ago) [shilongliu]
| * 32c5a2729 - Use github code scanning instead of LGTM (6 months ago) [shilongliu]
|/  
* aa731b96f - [azp]: Install libyang in azure pipeline (sonic-net#68) (8 months ago) [Hua Liu]
* 71b635d74 - Revert "[Azp]: Upgrade Azp to bullseye (sonic-net#49)" (sonic-net#66) (9 months ago) [Ze Gan]
* 7aa4e6fa4 - Adding Microsoft SECURITY.MD (sonic-net#58) (9 months ago) [microsoft-github-policy-service[bot]]

…-daemons (sonic-net#3420)

* advance pointer for sonic-platform-daemon to 9e2eb29e6e55a116b424faa63f510c7cdeeef7eb
[xcvrd] fix issue: xcvrd fails due to syntax error after sequential reboot (sonic-net#43)

* advance pointer for sonic-platform-common to ac7fde6e9ce532d450b3c43f354fc2f128053b4f
[sonic_sfp] fix syntax error in sfputilbase._read_eeprom_specific_bytes (sonic-net#58)

…tically (#25573)

#### Why I did it
src/sonic-dash-api
```
* 63d9cb2 - (HEAD -> 202511, origin/202511) [action] [PR:56] Add list of trusted VNIs (sonic-net#58) (8 hours ago) [mssonicbld]
* 694ce08 - [action] [PR:54] update docker slave name and switch to libboost1.83 (sonic-net#60) (26 hours ago) [mssonicbld]
```
#### How I did it
#### How to verify it
#### Description for the changelog

… (#24546)

#### Why I did it
src/dhcpmon
```
* 853ed44 - (HEAD -> 202505, origin/202505) Automated agent pool migration for branch 202505 (sonic-net#58) (11 days ago) [yijingyan2]
```
#### How I did it
#### How to verify it
#### Description for the changelog

[syseepromd] Prevent the syseepromd from termination (sonic-net#56)
 [thermalctld] Fix invalid warning status (sonic-net#58)

…ly (sonic-net#21342)

#### Why I did it
src/dhcprelay
```
* b4f59d0 - (HEAD -> 202311, origin/202311) [202311] Install corresponding dependency libs from 2002311 for PR check (sonic-net#58) (11 hours ago) [Yaqiang Zhu]
```
#### How I did it
#### How to verify it
#### Description for the changelog

1. Skip BGW nodes in pretest VTEP validation - BGW nodes have VIP VTEPs
   (cross-DC tunnel endpoints) that differ from leaf loopback VTEPs, causing
   false validation failures. Added 'bgw' guard consistent with verify_base_setup_bgw.

2. Add IPv6 Type-5 route prefixes (8000:x::/64) to get_expected_type5_routes() -
   Per SAG addressing, both IPv4 (80.x.0.0/24) and IPv6 (8000:x::/64) subnets
   are advertised as Type-5 routes. Previously only IPv4 was generated.

3. Remove erroneous 'neighbor TRANSIT activate' from generate_bgp_transit_wan_config
   ipv4 address-family - per reference config (dci_l2vni_l3vni_fullconfig_Feb24.txt
   lines 296-298), BGW WAN underlay only activates TRANSIT_WAN in ipv4 af. TRANSIT
   is the DC underlay peer-group, activated in ipv6 af by generate_bgp_underlay_config.

4. Document RM_SET_SRC6 BGW-only constraint in generate_source_route_maps() -
   already enforced by _DCI_ONLY_FEATURES guard in config_feature_dci, but added
   explicit docstring noting leaf nodes must never have RM_SET_SRC4/RM_SET_SRC6
   per reference config.