make the maude backend output more deterministic

@traiansf please review

The Maude backend had some issues that were making the output to maude JVM dependent. I added some code whose purpose is to ensure that the ordering and numbering of rules is the same accross different Java versions.
Also, how does it know when one output of one execution ends and the other one starts?  I mean, the output of one execution may spread over more than one line.  Is it that the `regex=true` option in `config.xml` assumes that in that case you would write `\n` for new lines in patterns?

I know I said it in the past, but I feel uneasy about this regex thing.  I thank you for solving the problem at the time, Dwight, but it just feels that this is not the long-term solution.  In this particular case, I would *not* use `regex=true` and I would have the cycle.out file have two solutions in it, the old-fashioned way.