DOC: Complete API for pixel_replace

[pllim]

Towards JP-4107

This PR addresses pixel_replace portion of #9793 . Only touch docs so should not need RT.

On main:

• https://jwst-pipeline.readthedocs.io/en/latest/jwst/pixel_replace/index.html

With this patch:

• https://jwst-pipeline--10536.org.readthedocs.build/en/10536/jwst/pixel_replace/index.html

Tasks

• If you have a specific reviewer in mind, tag them.
• add a build milestone, i.e. Build 12.0 (use the latest build if not sure)
• Does this PR change user-facing code / API? (if not, label with no-changelog-entry-needed)
  • write news fragment(s) in changes/: echo "changed something" > changes/<PR#>.<changetype>.rst (see changelog readme for instructions)
    • if your change breaks step-level or public API (as defined in the docs), also add a changes/<PR#>.breaking.rst news fragment
  • update or add relevant tests
  • update relevant docstrings and / or docs/ page
  • start a regression test and include a link to the running job (click here for instructions)
    • Do truth files need to be updated ("okified")?
      • after the reviewer has approved these changes, run okify_regtests to update the truth files
• if a JIRA ticket exists, make sure it is resolved properly

[pllim]

Is this acceptable change for a doc PR?

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 86.38%. Comparing base (a3708db) to head (60fc245).

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #10536      +/-   ##
==========================================
- Coverage   86.38%   86.38%   -0.01%     
==========================================
  Files         373      373              
  Lines       40068    40068              
==========================================
- Hits        34614    34612       -2     
- Misses       5454     5456       +2     

☔ 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.