fix: add labels to NodeNotFoundError for clearer messaging

[DharmaBytesX]

The error message now shows Branch:, Kind:, and Identifier: labels
instead of raw pipe-separated values, helping users understand
which branch the lookup failed on.

Before:

        Unable to find the node in the database.
        main | InfraDevice | {'name__value': 'bad-device404'}

After:

        Unable to find the node in the database.
        Branch: main | Kind: InfraDevice | Identifier: {'name__value': 'bad-device404'}

Changes

• python_sdk submodule updated with the fix
• Changelog entry added

Related

• SDK PR: fix: add labels to NodeNotFoundError for clearer messaging infrahub-sdk-python#1030
• Fixes bug: Better error message when cannot find a node #5514

---

Summary by cubic

Improved NodeNotFoundError messaging by adding labels for Branch, Kind, and Identifier, replacing the ambiguous pipe-separated string. Pulls in the fix via the python_sdk submodule update and adds a changelog entry; fixes #5514.

^{Written for commit 3f21188. Summary will update on new commits. Review in cubic}

[codspeed-hq]

Merging this PR will not alter performance

✅ 12 untouched benchmarks

---

_{Comparing DharmaBytesX:fix/5514-better-node-not-found-error (3f21188) with develop (46a56d6)}

[DharmaBytesX]

Hi! This updates the SDK submodule pointer and adds a changelog entry for the clearer NodeNotFoundError message (paired with opsmill/infrahub-sdk-python#1030). Would appreciate a review when you have a moment. Thanks!

[ogenstad]

I added a comment in the SDK repo here: https://github.com/opsmill/infrahub-sdk-python/pull/1030/changes#r3256789004

It's good to see that the pipeline ran and we don't have any tests that reacts to changes in the __str__ method.

One thing to note is that for pipelines running within this project we only ever merge the PRs that update the SDK submodule commit if those commits live in the stable, develop, infrahub-release branches or if they are from a tagged release. The reason is that other branches will get deleted and as such can cause later problems within the Infrahub repo.

Once the SDK PR is updated I also think we can close this commit since the change happened in that repo, and originally the issue #5514 should have been opened in the SDK repo since it's not strictly related to the Infrahub repo. (I'd not even consider that one a bug, it's more of a user preference, but it might still be nice to update the string).

[DharmaBytesX]

Thanks for the context on the submodule rule, that makes sense. I've pushed the rework on opsmill/infrahub-sdk-python#1030 addressing the review (required params on NodeNotFoundError, no conditional __str__, all call sites updated). Happy to either close this and re-open against a tagged/landed SDK commit, or leave it open as a tracker until #1030 merges, whatever you prefer.