Add professional README for modbus-device-maps

[Copilot]

The repository had a single-line README with no useful context for engineers evaluating or using the device maps.

Changes

• What Are Device Maps — explains register layout concept and the cost of manual mapping
• Supported Manufacturers — table of Schneider Electric, Siemens, ABB, SolarEdge, Eaton with device types; callout that maps here are preview/reference only
• Popular Device Maps — quick-reference table: PM8000, PAC4200, M4M, SE5000
• Why Use Device Maps — bullet list of engineer-focused value props (no manual register lookup, pre-validated scaling, instant connectivity)
• Getting Started — step-by-step with links to download, full doc library, and edition comparison
• Badges — XPF compatibility, docs, and license

Original prompt

Create a professional README for a repository that contains Modbus device maps used with Modbus Monitor XPF.

The README should:

• Explain what Modbus device maps are and why they are useful
• Highlight supported manufacturers such as Schneider Electric, Siemens, ABB, SolarEdge, Eaton
• Explain that these are preview or reference maps and the full experience is available in Modbus Monitor XPF
• Include links to:
  • https://docs.quantumbitsolutions.com/products/xpf/device-maps/
  • https://www.modbusmonitor.com/download
  • https://www.modbusmonitor.com/compare
• Emphasize that this helps engineers avoid manual register mapping
• Include a section "Popular Device Maps" listing:
  • Schneider PM8000
  • Siemens PAC4200
  • ABB M4M
  • SolarEdge SE5000
• Keep tone professional and targeted to engineers
• Add badges or sections if helpful (optional)
• Make it clean and readable in GitHub Markdown

---

⌨️ Start Copilot coding agent tasks without leaving your editor — available in VS Code, Visual Studio, JetBrains IDEs and Eclipse.