Create more tests of NeXus::File using based on old napi tests

[rboston628]

Description of work

Summary of work

This adds more tests or NeXus::File, which will be very important before we begin any work on removing napi. These tests are based on tests of napi, so should ensure continuity of behavior.

Related to #38332

Follow-on to PR #39010, adding tests taken from napi_test.cpp, originally written for napi.

Further detail of work

Writing this I had to compare to the napi_test.cpp file, and I got sick of the incessant

if(NXsomething(fileid, etc) != NXstatus::NX_OK) {
  std::cout << "some error message!\n;
  return TEST_FAILED;
}

cluttering it. So I introduced a macro to make these all one line. It should not change any behavior.

To test:

This is adding tests, and not messing with any functionality. Make sure the new tests pass.

---

Reviewer

Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

• Is the code of an acceptable quality?
• Does the code conform to the coding standards?
• Are the unit tests small and test the class in isolation?
• If there is GUI work does it follow the GUI standards?
• If there are changes in the release notes then do they describe the changes appropriately?
• Do the release notes conform to the release notes guide?

Functional Tests

• Do changes function as described? Add comments below that describe the tests performed?
• Do the changes handle unexpected situations, e.g. bad input?
• Has the relevant (user and developer) documentation been added/updated?

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.

[sf1919]

This one looks like a genuine test failure so I will leave it alone.

[peterfpeterson]

I don't know that the "all ok" messages are still needed since this is asserting things are equal.

[rboston628]

This was really helpful for debugging, especially with segfaults/stack overflows, to know that a test had definitively ended. But I can make them more descript.

[peterfpeterson]

Copying the tests over to NexusFile is a good step. I look forward to the c-api tests going away soon.