feat(eos): add show version with volatile-field exclusions

[garryshtern]

Pre-Request Checklist

• Passes rubocop code analysis
• Tests added or adapted
• Changes are reflected in the documentation
• User-visible changes appended to CHANGELOG.md

Description

Adds show version | no-more to the EOS model so that hardware identity
information (model, serial number, MAC addresses, software version, build
details) is captured alongside the running configuration.

The Uptime and Free memory lines are stripped with reject_lines
before the output is stored as a comment block. Without this exclusion
those two fields change on every poll cycle and would produce spurious
config-change events in git-based outputs.

Includes a device simulation fixture for a DCS-7050CX3-32S running
EOS 4.28.3M and the corresponding expected-output file.

🤖 Generated with Claude Code

[robertcheramy]

Out of curiosity - how much is from claude code and how much is from you?
I don't think claude code can generate a YAML simulation file and the corresponding output.

[garryshtern]

To answer your question honestly: this PR was entirely generated by Claude Code (claude-sonnet-4-6), directed by me. That includes the simulation YAML and the expected output.txt.

For the simulation YAML, Claude read several existing simulation files in the repo to learn the format, then constructed the YAML based on what a real EOS show version output looks like (with plausible but synthetic values for serial, MAC, version, etc.). The output.txt was generated by running atoms_generate.rb against that YAML.

I've addressed the CHANGELOG feedback:

• Moved the entry to the end of the Changed section
• Reworded to describe what show version captures (hardware identity) rather than mentioning implementation details
• Fixed the author to @garryshtern

[robertcheramy]

For the simulation YAML, Claude read several existing simulation files in the repo to learn the format, then constructed the YAML based on what a real EOS show version output looks like (with plausible but synthetic values for serial, MAC, version, etc.). The output.txt was generated by running atoms_generate.rb against that YAML.

I find it difficult that the simulation data doesn't come from a real device. If a test fails in the future I must trust that it is based on real data. If you only want to integrate the show real output, make something like: https://github.com/ytti/oxidized/blob/master/spec/model/data/aoscx%23CX10000_10.16.1020_environment%23simulation.yaml

Better would be to get real data with device2yaml, it is not difficult, see https://github.com/ytti/oxidized/blob/master/docs/DeviceSimulation.md

If you include AI-Generated simulation data, please mark it as such, for example with a comment at the beginn of the file.