doc(Modbus): add IModbusResponse documentation

[ArgoZhang]

Link issues

fixes #6771

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Add documentation for the IModbusResponse interface in the Modbus sample component

Documentation:

• Document the IModbusResponse interface definition with RawData and Builder properties
• Explain conversion extension methods ReadBoolValues and ReadUShortValues on IModbusResponse
• Show example of parsing RawData into custom business types like IEEE 754 32-bit floats

[sourcery-ai]

Reviewer's Guide

This PR enriches the Modbus sample documentation by introducing and explaining the IModbusResponse interface within the ModbusFactories.razor sample, detailing its properties and how to leverage its extension methods to convert raw Modbus data into useful types.

File-Level Changes

Change	Details	Files
Add IModbusResponse interface documentation	Inserted interface definition with RawData and Builder properties Explained purpose and structure of IModbusResponse	src/BootstrapBlazor.Server/Components/Samples/Modbus/ModbusFactories.razor
Provide usage examples of IModbusResponse extension methods	Described ReadBoolValues and ReadUShortValues methods Outlined how to extend RawData parsing for custom types like IEEE 754 float	src/BootstrapBlazor.Server/Components/Samples/Modbus/ModbusFactories.razor

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#6771	Add documentation for the IModbusResponse interface, including its definition and usage.	✅
#6771	Provide sample code demonstrating how to use IModbusResponse.	✅

Possibly linked issues

• doc(Modbus): add IModbusResponse documentation #6771: PR adds IModbusResponse documentation and samples, directly addressing the issue.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[Copilot]

Pull Request Overview

This PR adds documentation for the IModbusResponse interface to help developers understand how to work with Modbus read operation return values. It includes explanations of the interface properties, available extension methods, and guidance on creating custom data type extensions.

• Added comprehensive documentation for IModbusResponse interface including its properties and usage patterns
• Updated package dependencies to newer versions for Longbow libraries
• Provided examples of extension methods and custom data type conversion scenarios

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
ModbusFactories.razor	Added detailed documentation for IModbusResponse interface with usage examples
BootstrapBlazor.Server.csproj	Updated Longbow package versions to latest releases

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

Prompt for AI Agents

Please address the comments from this code review:

## Individual Comments

### Comment 1
<location> `src/BootstrapBlazor.Server/Components/Samples/Modbus/ModbusFactories.razor:99` </location>
<code_context>
+    <li><code>ReadUShortValues</code> 将 <code>IModbusResponse</code> 实例中 <code>RawData</code> 转换成无符号短整型数组 </li>
+</ul>
+
+<p>通过接口 <code>IModbusResponse</code> 获得到其原始数据 <code>RawData</code> 可以通过自定义扩展非常方便的扩展出符合自己业务的数据类型。如通过连续 2 个寄存器存储的数据，得到遵循 IEEE 754 标准的 32 位 <b>浮点数</b></p>
+
 <p>项目包含 Benchmark 基准测试工程</p>
</code_context>

<issue_to_address>
**suggestion:** Consider mentioning endianness when converting RawData to custom types.

Endianness can impact how custom types are interpreted from RawData. Noting this will help users avoid subtle bugs when extending functionality.

```suggestion
<p>通过接口 <code>IModbusResponse</code> 获得到其原始数据 <code>RawData</code> 可以通过自定义扩展非常方便的扩展出符合自己业务的数据类型。如通过连续 2 个寄存器存储的数据，得到遵循 IEEE 754 标准的 32 位 <b>浮点数</b></p>
<p><b>注意：</b>在将 <code>RawData</code> 转换为自定义类型（如 32 位浮点数）时，需要注意字节序（Endianness）。字节序会影响数据的解释方式，错误的字节序可能导致解析结果不正确。请根据实际设备或协议规范选择合适的字节序进行转换。</p>
```
</issue_to_address>

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (cedd988) to head (b0d2f71).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #6772   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          739       739           
  Lines        31713     31713           
  Branches      4463      4463           
=========================================
  Hits         31713     31713           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.