[Feature] ActionDiscretizer custom sampling

[oslumbers]

Description

Move the _custom_arange as a method of the ActionDiscretizer so that custom samplers can be implemented.

Motivation and Context

close #2608

• I have raised an issue to propose this change (required for new features and bug fixes)

Types of changes

What types of changes does your code introduce? Remove all that do not apply:

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds core functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation (update in the documentation)
• Example (update in the folder of examples)

Checklist

Go over all the following points, and put an x in all the boxes that apply.
If you are unsure about any of these, don't hesitate to ask. We are here to help!

• I have read the CONTRIBUTION guide (required)
• My change requires a change to the documentation.
• I have updated the tests accordingly (required for a bug fix or a new feature).
• I have updated the documentation accordingly.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/rl/2609

• 📄 Preview Python docs built from this PR

Note: Links to docs will display an error until the docs builds have been completed.

❌ 20 New Failures

As of commit d767eb3 with merge base 607ebc5 ():

NEW FAILURES - The following jobs have failed:

• Continuous Benchmark (PR) / CPU Pytest benchmark (gh)
  ##[error]Workflow failed! Resource not accessible by integration
• Continuous Benchmark (PR) / GPU Pytest benchmark (gh)
  ##[error]Workflow failed! Resource not accessible by integration
• Generate documentation / build-docs (3.10, 12.1) / linux-job (gh)
  ##[error]No files were found with the provided path: /home/ec2-user/actions-runner/_work/_temp/artifacts/. No artifacts will be uploaded.
• Habitat Tests on Linux / tests (3.9, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Libs Tests on Linux / unittests-gym (3.9, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Libs Tests on Linux / unittests-sklearn (3.9, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Lint / c-source / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Lint / python-source-and-configs / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• RLHF Tests on Linux / unittests (3.9, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• SOTA Tests on Linux / tests (3.9, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-cpu (3.10) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-cpu (3.11) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-cpu (3.12) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-cpu (3.9) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-cpu-oldget (3.12) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-gpu (3.11, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-olddeps (3.8, 11.6) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-optdeps (3.11, 12.1) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Linux / tests-stable-gpu (3.10, 11.8) / linux-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge
• Unit-tests on Windows / unittests-cpu / windows-job (gh)
  ##[error]fatal: couldn't find remote ref refs/pull/2609/merge

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[facebook-github-bot]

Hi @oslumbers!

Thank you for your pull request and welcome to our community.

Action Required

In order to merge any pull request (code, docs, etc.), we require contributors to sign our Contributor License Agreement, and we don't seem to have one on file for you.

Process

In order for us to review and merge your suggested changes, please sign at https://code.facebook.com/cla. If you are contributing on behalf of someone else (eg your employer), the individual CLA may not be sufficient and your employer may need to sign the corporate CLA.

Once the CLA is signed, our tooling will perform checks and validations. Afterwards, the pull request will be tagged with CLA signed. The tagging process may take up to 1 hour after signing. Please give it that time before contacting us about it.

If you have received this in error or have any questions, please contact us at [email protected]. Thanks!

[vmoens]

LGTM thanks!