ensure non-null project for domain and property descriptors

[labkey-klum]

Rationale

tracking issue

For both DomainDescriptor and PropertyDescriptor the project field has a not null database constraint. Recent changes to stop holding onto Container instances broke some of this when the container was root. This just restores the prior behavior and also updates the data views panel to show something more helpful than an empty dialog when errors like this occur.

Related Pull Requests

• ensure non-null project for domain and property descriptors #6971
• Regression for manage views exception testAutomation#2657

Tasks 📍

• Needs Automation
• Verify Fix @labkey-adam

[Copilot]

Pull Request Overview

This PR fixes non-null database constraint violations for the project field in DomainDescriptor and PropertyDescriptor classes, and improves error handling in the DataViewsPanel UI.

• Modified getProject() methods to return the container itself when no project is available, ensuring the project field is never null
• Enhanced error message display in DataViewsPanel to show specific exception details instead of generic "Failure" messages

Reviewed Changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated no comments.

File	Description
PropertyDescriptor.java	Updated getProject() to fallback to container when project is null
DomainDescriptor.java	Updated getProject() to fallback to container when project is null
DataViewsPanel.js	Improved error handling with descriptive failure messages

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}