chainlink [CRE-1205] explicitly state what role each node has

This pull request refactors the DON (Decentralized Oracle Network) TOML configuration files and documentation to remove the legacy bootstrap_node_index and gateway_node_index fields, replacing them with an explicit roles attribute for each node specification. This change improves clarity, flexibility, and maintainability of node role assignments across various DON types and example configurations.

Configuration and Documentation Refactoring:

Removed bootstrap_node_index and gateway_node_index fields from all DON TOML config examples, and updated documentation to reflect this change. Node roles are now assigned explicitly via the new roles attribute in each node spec. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
Updated all example configs to use the new roles field for node specification, assigning roles such as "bootstrap", "gateway", and "plugin" as appropriate for each DON. This change is reflected across workflow, gateway, Solana, Tron, and capabilities DON examples. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18]

Role Assignment and Node Specification Enhancements:

Each node's role is now explicitly defined in the roles array in the node_specs section, supporting multi-role nodes (e.g., both "bootstrap" and "gateway"), and clarifying per-node responsibilities. [1] [2] [3] [4] [5] [6] [7] [8]
Updated example node specs to include detailed configuration overrides and Docker-related settings, especially for plugin nodes, improving reproducibility and clarity for development and testing. [1] [2]

Override Mode Adjustments:

Changed override_mode from "all" to "each" in several configs to support per-node configuration, aligning with the new explicit role assignment mechanism. [1] [2]

Documentation Updates:

Updated README.md to explain the new node role assignment approach and removed references to the deprecated index-based role assignment. [1] [2] [3]

These changes modernize the DON configuration approach, making node role assignments more explicit and maintainable.

Oct 31 '25 17:10 Tofel

I see you updated files related to core. Please run pnpm changeset in the root directory to add a changeset as well as in the text include at least one of the following tags:

#added For any new functionality added.
#breaking_change For any functionality that requires manual action for the node to boot.
#bugfix For bug fixes.
#changed For any change to the existing functionality.
#db_update For any feature that introduces updates to database schema.
#deprecation_notice For any upcoming deprecation functionality.
#internal For changesets that need to be excluded from the final changelog.
#nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
#removed For any functionality/config that is removed.
#updated For any functionality that is updated.
#wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.