op-mode: T6586: add a distinct exception for unconfigured objects (as opposed to entire subsystems)

[dmbaturin]

Change Summary

Using UnconfiguredSubsystem when it's just one entity that isn't configured is overreaching, we likely want something more specific for those cases so that API clients can decide how to present the error to the user.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Code style update (formatting, renaming)
• Refactoring (no functional changes)
• Migration from an old Vyatta component to vyos-1x, please link to related PR inside obsoleted component
• Other (please describe):

Related Task(s)

Related PR(s)

Component(s) name

Op mode.

Proposed changes

The new UnconfiguredObject exception is a subclass of UnconfiguredSubsystems so clients can choose whether to differentiate them or not.

How to test

Smoketest result

Checklist:

• I have read the CONTRIBUTING document
• I have linked this PR to one or more Phabricator Task(s)
• I have run the components SMOKETESTS if applicable
• My commit headlines contain a valid Task id
• My change requires a change to the documentation
• I have updated the documentation accordingly

[github-actions]

👍
No issues in PR Title / Commit Title

[github-actions]

👍
No issues in unused-imports

[github-actions]

CI integration ❌ failed!

Details

CI logs

• CLI Smoketests ❌ failed
• Config tests 👍 passed
• RAID1 tests 👍 passed