Remove deprecated coveragerc file

[opotowsky]

Description

There was a stale copy of a coverage config file in armi/resources. It's existence was only dreamed up to prevent the issues with dot-files on a Windows cluster. I changed the coverage work in case.py to copy the main coverage config file to a file name without a dot instead. Voila! No more forgetting to maintain multiple files.

---

Checklist

• This PR has only one purpose or idea.
• Tests have been added/updated to verify that the new/changed code works.

• The code style follows good practices.
• The commit message(s) follow good practices.

• The release notes (location doc/release/0.X.rst) are up-to-date with any bug fixes or new features.
• The documentation is still up-to-date in the doc folder.
• The dependencies are still up-to-date in setup.py.

[opotowsky]

@john-science My history is a little mucked up from the interactive rebase. Working on fixing

[opotowsky]

Hey @john-science What happened with CI? Is there a way to kick it back off without making, e.g., an empty commit?

[jakehader]

Hey @john-science What happened with CI? Is there a way to kick it back off without making, e.g., an empty commit?

I think making an empty / trivial commit is the only way that I can see to easily kick off the CI again for GitHub. There isn't an easy "rerun all" since we have different GitHub actions that get fired off in parallel. That is my recommendation, but maybe @john-science has a more elegant solution.

[opotowsky]

The coverage drop would be expected, since I added coverage-related code that can't be unit tested.

[john-science]

It looks to me like you could make this simpler:

if platform...
    if makeCopy...
        # Make ...

covFile = os.path.join(covRcDir, ".coveragerc")

It just looks like that else is unnecessary, and you could have the covFile = line once instead of twice. Right?

[john-science]

I love removing the old cruft in the system!

Thanks!