Allow model names to contain periods

[agile]

We are probably outliers here, but our models often have periods in their names which is not handled very well by the model/explore filtering.

Alternatively, I wonder if we could we use another delimiter than period, such as a slash '/' instead?

[codecov]

Codecov Report

Merging #121 into master will increase coverage by 0.87%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #121      +/-   ##
==========================================
+ Coverage   65.16%   66.04%   +0.87%     
==========================================
  Files           9        9              
  Lines         709      692      -17     
==========================================
- Hits          462      457       -5     
+ Misses        247      235      -12

Impacted Files	Coverage Δ
spectacles/validators.py	59.65% <100%> (+2.66%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 699ea9a...e8730f1. Read the comment docs.

[DylanBaker]

@agile I somehow didn't realise you could have periods in a model name. Do you know if it is possible to have them in explore names?

I am inclined to think that you're correct about this being an outlier instance, but we should solve it nonetheless. I do think it would be easiest to take the alternative approach and just delimit on something that can't be in model or explore names. @joshtemple Do you have a strong preference?

[iserko]

Why not just separate it into two CLI parameters.

# current (specific explore)
--explores mymodel.myexplore
# would be replaced by
--model mymodel --explore myexplore

# current (whole model)
--explores mymodel.*
# would be replaced by
--model mymodel

# current (a specific explore in all models)
# this shouldn't be possible now anyway, but not sure if the code catches it
# or maybe it is something people actually need to run against?
--explores *.myexplore
# should definitely fail in the new parser if you don't specify --model as well
--explore myexplore

[DylanBaker]

How would you want it to work if you were interested in testing explores across multiple models.

i.e. in the current setup:

--explores model_one.explore_one model_two.explore_two

[DylanBaker]

@agile It looks like a slash / should work. It isn't allowed in either a model or an explore name, which solved this problem. That would be our preferred solution I think.