[ENH] Allow microxs reader to handle files w/o nfy data

[drewejohnson]

Closes #464

Originally written by Andrea Alfonsi in #465

Please add the appropriate tag to the beginning of the title of your PR:

1. [DOC] if documentation related
2. [DEP] if something is deprecated or a deprecated feature is removed
3. [ENH] if a feature or enhancement
4. [BUG] if a bug fix
5. [API] if a (possibly incompatible) change to the API
6. [TST] if related to our test suite
7. [STY] if related to code cleanliness and pythonicness

For bug fixes and enhancements, link to the corresponding issue.

Make sure you have read over the developer guide to ease the review process. These include:

• [ x] PR fits the project scope
• [ x] Code to be committed is DRY and matches the code style of the project
• [ x] New and/or changed features are well documented and have adequate testing
• [ x] For first-time contributors, you have included your attribution in docs/contributors.rst

Include a thorough and concise overview of the changes, and why this PR is overall beneficial to the project.

Once the PR has been created and is nearing closure, make sure that serious changes, including deprecations and incompatible changes are documented in the changelog