Research and proof-of-concept only running unit test of microservice where changes are made

[jaredb96]

We don't need to run all the unit tests every time we make a code change. I think it would be cost effective to run them in hmda-platform (our most important service) as well as whichever microservice actually had code changes. For ex: If we make a change to our institutions api, we should only run hmda-platform and institutions api unit tests, not something else like quarterly graphs. This ticket is to research whether that is feasible and doable. If it isn't it will be documented why here.