APP-226 - Initial Report Execution Service Scaffolding

[JordanGuinn]

Description

This PR introduces some initial scaffolding to establish the new Python-based report execution "service" within NEDSS-Modernization, built with uv and FastAPI. It also includes:

• Introduces pytest for, well, testing, and introduces some rudimentary tests
• Introduces ruff for linting and formatting
  • I ended up picking this simply because it's also provided by the creators of uv, but open to suggestions!
• Adds a GitHub Action for linting, formatting and running tests

Tickets

• Jira Ticket

Checklist before requesting a review

• PR focuses on a single story
• Code has been fully tested to meet acceptance criteria
• PR is reasonably small and reviewable (Generally less than 10 files and 500 changed lines)
• All new functions/classes/components reasonably small
• Functions/classes/components focused on one responsibility
• Code easy to understand and modify (clarity over concise/clever)
• PRs containing TypeScript follow the Do's and Don'ts
• PR does not contain hardcoded values (Uses constants)
• All code is covered by unit or feature tests

[mcmcgrath13]

🧑‍🔬

[mcmcgrath13]

(q, b): if you already manage python another way, do you need to do this part?

[JordanGuinn]

You shouldn't! Will update to indicate it as optional.

[mcmcgrath13]

(sugg, nb): do we want a nested .gitignore in the service vs adding to the outer? this seems to be a common pattern

[JordanGuinn]

Definitely! This was initially my preference, but I didn't want to apply that if others felt differently - will update!

[emyl3]

(❓, blocking) I remember when working on this we wanted to mindful of which 3rd party actions we are using. (Please correct me if I misunderstood @mcmcgrath13) Is this accepted by the CDC? 🤔

[mcmcgrath13]

@emmastephenson do you know if that's a concern for cdcgov like it is for cdcent?

[emmastephenson]

I remember a conversation with Boris about this at some point, but I sure can't find it now 😵‍💫 I think it should be fine to add this one, though! Looks like it's already in use across CDCGov so I don't expect adding it here will be a problem.

[emyl3]

Thank you Emma and Mary!!!

[emyl3]

(❓, blocking) We use already use this port -- should this be something else to not clash? 👀

[JordanGuinn]

Yep, good catch! I noticed that as well in the separate branch for the docker-compose work - will update here!

[mcmcgrath13]

Suggested change

	"fastapi[standard]>=0.128.0",
	"pydantic>=2.12.5",
	"fastapi[standard]~=0.128.0",
	"pydantic~=2.12.5",

(sugg, b): to make sure we're on the expected major version

[mcmcgrath13]

though that would only help with the patch at the level of specificity 🤔 , which for fastapi is probably good, but maybe pydantic~=2.12 🥴 TIL python's version specifiers lack some expressivity...

[mcmcgrath13]

Suggested change

	"pytest>=9.0.2",
	"ruff>=0.15.0",
	"pytest~=9.0",
	"ruff~=0.15.0",