Reloading a lazy module that has not yet been materailized should be no-op

Bug report

Bug description:

Reloading a not-yet materialized lazy module is not supported well. It makes sense for the reloading in this case to be no-op since when the actual loading happens e.g. by accessing an attribute, the new code will be loaded anyway. Currently, the reload tries to reload the module while its loaded is lazy in the first place.

CPython versions tested on:

3.13, 3.12, 3.14, CPython main branch

Operating systems tested on:

Linux

Linked PRs

• gh-139857
• gh-142649
• gh-143584

首先查看連結的 PR gh-139857、gh-142649 和 gh-143584，因為它們展示了針對此行為已經提出的工作。追蹤 lazy module 的 reload 路徑，並驗證在 materialization 之前 reload 是 no-op，而之後的屬性存取仍會載入更新後的程式碼；完成時應包含回歸覆蓋。