restrict classical action of certain arithmetic bloqs

[NoureldinYosri]

• SubtractFrom.on_classical_values was using math.fmod which fails in the case of overflow ... using simulation.classical_sim.add_ints instead
• bloqs for modular arithmetic assume that their inputs are in the correct range $[0, \mod)$ ... fixing the classical action is easy for them ... but the decompositions/constructions will fail on those inputs since they were not designed to handle them.

fixes #1515

[anurudhp]

should we instead raise a ValueError for out-of-bounds inputs? (similar to e.g. BQUInt.assert_valid_classical_val).

[NoureldinYosri]

depends on how you define the bloq ... if we want the bloq to be unitary then the classical action is correct and we don't need to raise an error

however constructions assume valid range ... I don't feel strongly towards either ... although I'm a bit leaning towards raising an error to match the construction

[mpharrigan]

I'd prefer that the classical action raises an error. The tensors-from-classical-action function would need to handle this, of course

[NoureldinYosri]

done