InternalsVisibleTo NHibernate.Test

[gliljas]

Allowing the test project to access internal types and members in the main project opens up for cleaner and less brittle tests, without having to resort to file linking or reflection. It potentially triggers internalizing things that ideally should be private, but I think that's a smaller issue.

Since the NHibernate assembly is strong named, this required the same thing for NHibernate.Test and NHibernate.DomainModel. Potentially, the entire strong naming could be toggled off in build scenarios where it's not needed. Not done here, but the PropertyGroups etc. have been kept separate, so that they can be made conditional.

[Copilot]

Pull Request Overview

This PR enables the NHibernate.Test project to access internal types and members from the main NHibernate project through the InternalsVisibleTo attribute, allowing for cleaner and less brittle tests.

• Adds InternalsVisibleTo attribute to expose NHibernate internals to the test project
• Enables strong naming for NHibernate.Test and NHibernate.DomainModel assemblies to satisfy strong naming requirements
• Removes file linking for internal classes now that they're accessible via InternalsVisibleTo

Reviewed Changes

Copilot reviewed 4 out of 4 changed files in this pull request and generated 2 comments.

File	Description
src/NHibernate/NHibernate.csproj	Adds InternalsVisibleTo attribute with public key for NHibernate.Test
src/NHibernate.Test/NHibernate.Test.csproj	Enables strong naming and removes file linking for internal classes
src/NHibernate.Test/ExceptionsTest/OracleClientExceptionConverterExample.cs	Updates Oracle exception handling to use reflection instead of direct type access
src/NHibernate.DomainModel/NHibernate.DomainModel.csproj	Enables strong naming to maintain assembly compatibility