fix: NetworkBehaviour inspector view exceptions when using a distributed authority network topology (#3578)

This PR addresses an issue where `NetworkBehaviour` could throw an
exception if viewed within the inspector view during a distributed
authority network topology based session and using a DAHost that is not
the authority of the associated `NetworkObject`.

This PR also addresses the issue where the authority does not have
editable inspector view fields when viewed by the authority during a
distributed authority session.


## Changelog

-Fixed: Issue where viewing a `NetworkBehaviour` with one or more
`NetworkVariable` fields could throw an exception if running a
distributed authority network topology with a local (DAHost) host and
viewed on the host when the host is not the authority of the associated
`NetworkObject`.

-Fixed: Issue when using a distributed authority network topology and
viewing a `NetworkBehaviour` with one or more `NetworkVariable` fields
in the inspector view would not show editable fields.

## Testing and Documentation

- No tests have been added.
- No documentation changes or additions were necessary.
- Manually testing this is required to validate.

<!-- Uncomment and mark items off with a * if this PR deprecates any
API:
### Deprecated API
- [ ] An `[Obsolete]` attribute was added along with a `(RemovedAfter
yyyy-mm-dd)` entry.
- [ ] An [api updater] was added.
- [ ] Deprecation of the API is explained in the CHANGELOG.
- [ ] The users can understand why this API was removed and what they
should use instead.
-->

## Backport

This is a v2.x distributed authority specific issue. No back port is
needed.

<!-- If this is a backport:
 - Add the following to the PR title: "\[Backport\] ..." .
 - Link to the original PR.
If this needs a backport - state this here
If a backport is not needed please provide the reason why.
If the "Backports" section is not present it will lead to a CI test
failure.
-->

Author: NoelStephensUnity

com.unity.netcode.gameobjects/CHANGELOG.md

@@ -10,6 +10,19 @@ Additional documentation and release notes are available at [Multiplayer Documen
 
 ### Added
 
+
+### Fixed
+
+- Fixed issue where viewing a `NetworkBehaviour` with one or more `NetworkVariable` fields could throw an exception if running a distributed authority network topology with a local (DAHost) host and viewed on the host when the host is not the authority of the associated `NetworkObject`. (#3578)
+- Fixed issue when using a distributed authority network topology and  viewing a `NetworkBehaviour` with one or more `NetworkVariable` fields in the inspector view would not show editable fields. (#3578)
+
+### Changed
+
+
+## [2.5.0] - 2025-08-01
+
+### Added
+
 - Added serializer for `Pose` (#3546)
 - Added methods `GetDefaultNetworkSettings` and `GetDefaultPipelineConfigurations` to `UnityTransport`. These can be used to retrieve the default settings and pipeline stages that are used by `UnityTransport`. This is useful when providing a custom driver constructor through `UnityTransport.s_DriverConstructor`, since it allows reusing or tuning the existing configuration instead of trying to recreate it. This means a transport with a custom driver can now easily benefit from most of the features of `UnityTransport`, like integration with the Network Simulator and Network Profiler from the multiplayer tools package. (#3501)
 - Added mappings between `ClientId` and `TransportId`. (#3516)

com.unity.netcode.gameobjects/Runtime/Core/NetworkBehaviour.cs

@@ -529,11 +529,21 @@ public bool IsSessionOwner
 
         internal bool IsBehaviourEditable()
         {
-            // Only server can MODIFY. So allow modification if network is either not running or we are server
-            return !m_NetworkObject ||
-                m_NetworkObject.NetworkManager == null ||
-                m_NetworkObject.NetworkManager.IsListening == false ||
-                m_NetworkObject.NetworkManager.IsServer;
+            if (!m_NetworkObject)
+            {
+                return true;
+            }
+
+            if (!m_NetworkObject.NetworkManager)
+            {
+                return true;
+            }
+
+            var networkManager = m_NetworkObject.NetworkManager;
+
+            // Only the authority can MODIFY. So allow modification if network is either not running or we are the authority.
+            return !networkManager.IsListening ||
+                ((networkManager.DistributedAuthorityMode && m_NetworkObject.IsOwner) || (!networkManager.DistributedAuthorityMode && networkManager.IsServer));
         }
 
         //  TODO: this needs an overhaul.  It's expensive, it's ja little naive in how it looks for networkObject in