docs: Clarify DCBX requirement vs DCBX willing mode in TOR QoS reference

## Summary

The TOR QoS Policy reference doc creates customer confusion about DCBX configuration. Customers are making a logical leap from "DCBX must be enabled to advertise the required TLVs" to "DCBX willing mode should be true." This is incorrect. Azure Local does **not** support DCBX willing mode — only a **static** configuration is supported.

**Affected doc:** [Reference-TOR-QOS-Policy-Configuration.md](https://github.com/Azure/AzureLocal-Supportability/blob/main/TSG/Networking/Top-Of-Rack-Switch/Reference-TOR-QOS-Policy-Configuration.md)

**Referenced from:** [Physical network requirements](https://learn.microsoft.com/en-us/azure/azure-local/concepts/physical-network-requirements?view=azloc-2604&tabs=24H2reqs)

## Customer Confusion

The current language describes enabling DCBX as a required aspect of switch configuration. This is true in the sense that DCBX must be enabled to advertise all the TLV values required for Azure Local (carried in LLDP frames). However, customers are inferring that DCBX willing mode should also be enabled.

## What's Correct

- DCBX **enabled**: required to advertise the necessary TLVs over LLDP.
- DCBX **willing mode**: **not supported** in Azure Local. Configuration must be **static**.

## Why DCBX Willing Mode Is Not Supported

DCBX willing mode allows the fabric to dynamically change host-level settings. The fabric does not understand Azure Local's RDMA / storage requirements, and dynamic changes from the fabric can disrupt RDMA traffic and impact the storage layer. If DCBX willing mode were enabled, a rogue configuration could change neighbor settings and break system configurations.

This is not a new requirement — it has been in place since Storage Spaces Direct originally launched.

## Requested Change

Update the TOR QoS reference doc to:

1. Explicitly state that DCBX **willing mode must be disabled / false** (static configuration only).
2. Distinguish between "DCBX enabled (for TLV advertisement)" and "DCBX willing mode (not supported)".
3. Briefly explain *why* willing mode is not supported (RDMA / storage traffic protection), so customers understand the rationale and don't try to enable it.

## Scope

Small documentation fix. No behavior change.

TSG/Networking/Top-Of-Rack-Switch/Reference-TOR-QOS-Policy-Configuration.md から始め、その DCBX に関する記述を、TLV アドバタイズメントが有効であることと willing mode の違いについて issue が示している区別と比較してください。willing mode が無効であり、RDMA/storage の理由により静的構成が必要であることを明記するようリファレンスを更新してください。要求された 3 つの明確化事項がすべて明示されれば完了です。

索引モデルが issue の本文から書いたものです。