Move compute logs utility scripts

[mlarose]

Summary & Motivation

Relates to #21920

How I Tested These Changes

Tested with ./examples/deploy_docker/from_source/build.sh docker-compose set + launching a run to verify the problem is addressed

[gibsondan]

seems reasonable to me, there may also be a way to invoke the script so that it doesn't try to pick up local imports? Maybe by invoking it as a module with -m rather than as a file? but this solution requires less knowledge of python arcana so is probably worth doing either way

[mlarose]

seems reasonable to me, there may also be a way to invoke the script so that it doesn't try to pick up local imports? Maybe by invoking it as a module with -m rather than as a file? but this solution requires less knowledge of python arcana so is probably worth doing either way

Short answer, I don't know. I don't see the advantage over a different loading method vs just segregating the offenders in their own folder, and I wanted to fix quickly in case a hotfix was deemed necessary.

I like the fact that I am isolating scripts that aren't really part of the code that should be loaded in the module in their own folder. the only reason there is an __init__.py is because how the path is discovered (import then .file)

[prha]

Seems reasonable to me.