Validate only submitted Project Euler solution

[dhruvmanila]

Messing around with GitHub Actions, trying to see if this is possible:
We will run checks only on the submitted Project Euler solution and not all.

Describe your change:

• Improve Project Euler validate solutions script
• Add an algorithm?
• Fix a bug or typo in an existing algorithm?
• Documentation change?

Checklist:

• I have read CONTRIBUTING.md.
• This pull request is all my own work -- I have not plagiarized.
• I know that pull requests will not be merged if they fail the automated tests.
• This PR only changes one algorithm file. To ease review, please open separate PRs for separate algorithms.
• All new Python files are placed inside an existing directory.
• All filenames are in all lowercase characters with no spaces or dashes.
• All functions and variable names follow Python naming conventions.
• All function parameters and return values are annotated with Python type hints.
• All functions have doctests that pass the automated testing.
• All new algorithms have a URL in its comments that points to Wikipedia or other similar explanation.
• If this pull request resolves one or more open issues then the commit message contains Fixes: #{$ISSUE_NO}.

[dhruvmanila]

Is this useful? @cclauss

I was messing around with GitHub Actions and wrote some functions so that the validate_solutions script only checks for the submitted solution and if there are none, it will default to check all solutions. Also, I have scheduled this to be run every day for all solutions in case we break something.

[cclauss]

Draft usually means not yet ready for review.

[ghost]

Pull Request Report

@dhruvmanila Hello! I'm a bot made to check all the pull request Python files. First of all, I want to say thank you for your time and interest in this project and for opening a pull request. There seems to be missing requirements in some of the Python files submitted in this pull request. Please read through the report and make the necessary changes. You can take a look at the relevant links provided after the report.

What are node paths? 🔽

The report contains headings and a checklist where the items are paths to the class/function/parameter where the requirement is missing. Node paths are double colon :: separated names and can be in any of the following format:

• Class path: [file_name]::[class_name]
• Function path: [file_name]::[function_name]
• Function parameter path: [file_name]::[function_name]::[parameter_name]
• Method path: [file_name]::[class_name]::[function_name]
• Method parameter path: [file_name]::[class_name]::[function_name]::[parameter_name]

Following functions require tests [doctest/unittest/pytest]:

• scripts/validate_solutions.py::convert_path_to_module
• scripts/validate_solutions.py::all_solution_file_paths
• scripts/validate_solutions.py::get_files_url
• scripts/validate_solutions.py::added_solution_file_path
• scripts/validate_solutions.py::collect_solution_file_paths
• scripts/validate_solutions.py::test_project_euler

Relevant links 🔽

• Contributing guidelines
• Project Euler solution guidelines
• Type hints
• doctest
• unittest
• pytest

[dhruvmanila]

Note to me: Configure the bot to ignore the scripts/ directory.

[dhruvmanila]

Draft usually means not yet ready for review.

Sorry for that, I just wanted you to a second opinion on whether this was worth doing.