[bsp/allwinner] feat: porting to RT_USING_DEVICE_OPS

[polarvid]

拉取/合并请求描述：(PR description)

[

为什么提交这份PR (why to submit this PR)

This patch ports the codebase to use the RT_USING_DEVICE_OPS structure, which is required by v5.1.0 Smart kernel, improves modularity and makes it easier to manage device operations by consolidating them into a single structure, enhancing maintainability and future scalability.

你的解决方案是什么 (what is your solution)

Changes:

• Added RT_USING_DEVICE_OPS conditionals to partition.c and drv_sdmmc.c.
• Defined rt_device_ops structures for partition and sdmmc drivers.
• Updated device initialization to use the ops structure if defined.
• Replaced direct function calls with rt_dev_control, rt_dev_read, and rt_dev_write macros where applicable.
• Removed redundant us_delay function from os.c.

请提供验证的bsp和config (provide the config and bsp)

• BSP: allwinner d1s

• .config:

• action:

]

当前拉取/合并请求的状态 Intent for your PR

必须选择一项 Choose one (Mandatory):

• 本拉取/合并请求是一个草稿版本 This PR is for a code-review and is intended to get feedback
• 本拉取/合并请求是一个成熟版本 This PR is mature, and ready to be integrated into the repo

代码质量 Code Quality：

我在这个拉取/合并请求中已经考虑了 As part of this pull request, I've considered the following:

• 已经仔细查看过代码改动的对比 Already check the difference between PR and old code
• 代码风格正确，包括缩进空格，命名及其他风格 Style guide is adhered to, including spacing, naming and other styles
• 没有垃圾代码，代码尽量精简，不包含#if 0代码，不包含已经被注释了的代码 All redundant code is removed and cleaned up
• 所有变更均有原因及合理的，并且不会影响到其他软件组件代码或BSP All modifications are justified and not affect other components or BSP
• 对难懂代码均提供对应的注释 I've commented appropriately where code is tricky
• 代码是高质量的 Code in this PR is of high quality
• 已经使用formatting 等源码格式化工具确保格式符合RT-Thread代码规范 This PR complies with RT-Thread code specification

[polarvid]

@ylyamin you could check the PR message or the commit log for details 😉

[BernardXiong]

这些使用rt_device_* API是否更合适些？

[polarvid]

rt_device API 有特殊的操作协议 （open, init），但是 allwinner HAL 实现 API 没有遵循这种协议。这就导致对接后驱动工作异常（驱动内部直接 read 没有 open，无法通过引用计数检查。也可以理解为驱动内部是通过 dev-ops 调内部 API 的，因此不遵循外部操作协议）。

因此建议是建个 issue，后续工作中继续推进驱动的 API 对接问题。本 PR 还是保留宏的形式。

[polarvid]

tested with commit c7e1982 on 柿饼 M7