Expand project scripts to work with issues too

[jennyhickson]

PR Summary

Sci/Tech Reviewer:
Code Reviewer: @james-bruten-mo

Expand the current Project scripts to work with both the Issue and Pull requests, and expand the milestone script to also finish issues:

• Change ProjectData class to work with issues and pull requests
• Change PullRequest class into a ProjectItem base class, with PullRequest and Issue child classes
• Add checks for outstanding In Review issues before closing milestone
• Refactor checks using new count_items routine
• Remove all remaining open issues from the milestone
• Rename test data from the review tracker to pr.json and add test data from the issue tracker

Also(!) add a new script for any project maintenance that happens at the CR deadline. Currently this just removes issues that don't have a linked PR from the milestone.

Code Quality Checklist

• I have performed a self-review of my own code
• My code follows the project's style guidelines
• Comments have been included that aid understanding and enhance the readability of the code
• My changes generate no new warnings
• All automated checks in the CI pipeline have completed successfully

Testing

• This change has been tested appropriately (please describe)

Security Considerations

• I have reviewed my changes for potential security issues
• Sensitive data is properly handled (if applicable)
• Authentication and authorisation are properly implemented (if applicable)

AI Assistance and Attribution

• Some of the content of this change has been produced with the assistance of Generative AI tool name (e.g., Met Office Github Copilot Enterprise, Github Copilot Personal, ChatGPT GPT-4, etc) and I have followed the Simulation Systems AI policy (including attribution labels)

Sci/Tech Review

• I understand this area of code and the changes being added
• The proposed changes correspond to the pull request description
• Documentation is sufficient (do documentation papers need updating)
• Sufficient testing has been completed

(Please alert the code reviewer via a tag when you have approved the SR)

Code Review

• All dependencies have been resolved
• Related Issues have been properly linked and addressed
• Code quality standards have been met
• Tests are adequate and have passed
• Security considerations have been addressed
• Performance impact is acceptable

[james-bruten-mo]

Nothing major

[james-bruten-mo]

Does this work? Surely you'll need a different variable name?

[jennyhickson]

weirdly it does seem to, but I've changed it for clarity

[james-bruten-mo]

Docstring :)

[jennyhickson]

done

[james-bruten-mo]

Looks good, cheers