Added ActionSpaceConfig

[ppasupat]

Description

Added ActionSpaceConfig for custom action spaces.

• Select a custom list of actions to include.
• For coordinates, added support for binned coordinates (divide the screen with a grid, then click the middle of a grid cell).

Fixes #26.

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Checklist:

• I have run the pre-commit checks with pre-commit run --all-files (see CONTRIBUTING.md instructions to set it up)
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[pseudo-rnd-thoughts]

Changes look good, I just have a question on if the functions should be methods or just functions

[pseudo-rnd-thoughts]

Do we want get_action_space and get_raw_coords as ActionSpaceConfig methods

[ppasupat]

I have moved the methods to ActionSpaceConfig.

[pseudo-rnd-thoughts]

I don't think we should be including tests in the release

[ppasupat]

I added that line to trigger pyright on presubmit. Is there a different way to trigger pyright on tests?

[pseudo-rnd-thoughts]

Sorry I thought this line was for the files that are included in the release.
You are correct, this is the correct way of adding tests to pyright.
Though I should note that we normally don't care about having correct type hints for the tests

[ppasupat]

Thanks. It still helps with catching mistakes like missing method arguments, so I would prefer to keep it here for now.