Fixed .bad mismatches due to strengthened const checking
Merge pull request #162 from vasslitvinov/fixed-.bad-mismatches-for-const-checking

Fixed .bad mismatches due to strengthened const checking.

[autoCopyWithBegin discussed with Sung;
 initCopyWithBegin to be reviewed post-commit, for expediency]

In both tests a field of a record formal passed by blank intent
was modified. Since #157 this is flagged as an error,
shadowing the issues that the tests expose.

In autoCopyWithBegin, I simply changed the formal to have 'in' intent.

In initCopyWithBegin, neither 'in' nor 'ref' intent worked.
I.e. the compiler issued unrelated errors, due to the way
chpl__initCopy is handled and utilized by the compiler.

So instead I made the test modify another variable.
IMO this preserves the spirit of the test, which is that
a 'begin' block results in an extra formal of chpl__initCopy,
and that causes issues. I.e. it does not matter what happens
in the begin block.

While there, I added autoCopyWithBegin.compopts with "--verify".
This way an issue is caught earlier in the compiler.
FYI without --verify the symptom is the same as for initCopyWithBegin.

I did not add --verify for initCopyWithBegin, because it does not affect
the symptom.