Add FEATURES.yml documentation for Wannier90, Gaussian, ORCA, ABINIT, and Wien2k parsers

[Copilot]

Extends parser feature documentation to five additional parsers following the standardized runschema terminology introduced in the initial batch.

Changes

• Wannier90 - Wannierization capabilities: MLWF construction, tight-binding Hamiltonian generation, hopping matrices, Wannier interpolation for bands/DOS
• Gaussian - Molecular quantum chemistry: DFT/post-HF methods (MP2-MP5, CCSD, CI), 100+ XC functionals, vibrational analysis, thermochemistry
• ORCA - Spectroscopy-focused: DFT/hybrid/double-hybrid functionals, local correlation methods (DLPNO-CCSD(T)), SCF convergence tiers
• ABINIT - Beyond-DFT: GW approximations (G0W0, ev-scGW, qp-scGW), BSE for excitons, DFPT phonons, multi-dataset workflows
• Wien2k - All-electron FP-LAPW+lo: APW+lo basis, mBJ for accurate band gaps, comprehensive meta-GGA support, core-hole spectroscopy

Each FEATURES.yml follows the established structure:

• Metadata with timestamp and model attribution (GitHub Copilot)
• Parser info (name, homepage, mainfile patterns)
• Runschema capabilities by section (run, method, system, calculation, workflow)
• Special features and implementation notes

All files use consistent NOMAD runschema terminology as specified in .github/copilot-instructions.md.

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[ndaelman-hu]

TODO: double-check the specific details like properties and file formats with a local model

[ndaelman-hu]

@ndaelman-hu double-check

[ndaelman-hu]

Okay, this was pulled from the tableOfFiles in the entry-points, but I don't think this is representative of the parser capacity. It more so lists all possible target files.

I guess it would be better to turn this into a table, were those that are supported are marked.

[ndaelman-hu]

This gave me 3 TODOs for the main instruction set:

• tell Copilot to update whenever a parser is extended.
• request that the file support is handled in a table.
• request a source for each property covered to prevent hallucination (too much?)