ClimaCoreTempestRemap parameter checking

**Is your feature request related to a problem? Please describe.**
Certain parameters cause TempestRemap to fail with an undescriptive error, which makes debugging very difficult. This seems to often be caused by constructing a topology with unsupported values of `ne` or `Nq`, which then gets passed into [write_exodus](https://github.com/CliMA/ClimaCore.jl/blob/main/lib/ClimaCoreTempestRemap/src/exodus.jl#L20) and fails.

**Describe the solution you'd like**
We should add assertions to the TR wrappers to prevent the code from reaching TR itself with an invalid topology, and to provide descriptive error messages when failures occur.

Start with the TR wrappers that construct topologies and the write_exodus entry point in lib/ClimaCoreTempestRemap/src/exodus.jl. Trace how ne and Nq reach TempestRemap, then add validation and descriptive failures; done means invalid topologies are rejected before TR and errors explain the bad parameters.

Written by the indexing model from the issue text.