docs: clarify reward kernel flags

[william-xue]

Summary

• Clarify how Grid2Op reward classes receive contextual flags in addition to the usual MDP reward-kernel inputs.
• Explain that these flags distinguish the agent-submitted action from the action effectively applied by the environment, e.g. when an out-of-bounds redispatching action is replaced by do-nothing.

Validation

• git diff --check
• python3 content check for the added reward documentation note

Closes #737

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[codacy-production]

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

_{NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.}

[BDonnot]

Hello,

Thanks again for this fix.

Same (minor) issue as for the your other one. You did not signoff (Developer Certificate of Origin (DCO) ) your commit.

Doing it is really easy in your case, you simply need, locally to type:

git commit --amend -s
git push --force

should do the trick.

The first line will simply add a "signed off by " in the message commit, which is required to contribute to open source projects hosted by the linux fundation. See https://developercertificate.org/ for more information.

Thanks again and let me know if you encounter any issues

[william-xue]

Thanks for pointing this out. I amended the commit locally with a DCO sign-off; pushing the rewritten branch requires force-with-lease, so I will update the PR branch as soon as that guarded push is allowed.