change question copy naming scheme

change from question, question-n to question, copy-n-of-question

Copy question introduced some unexpected side effects where the way
copies of questions were named caused questions to get intertangled when
you renamed the copy and momentarily had the same name as the old one.

In attempting to fix this https://github.com/dimagi/Vellum/pull/69 I
made select item itext ids always automatically generated.  This had the
unfornate side-effect of making it impossible to copy a select question
with numeric item values without having immediately overlapping itext
ids.

This change avoids that but should also avoid any other rename issues.

To be more robust, we should also

- make the question id and item value inputs only fire on change, not
  textchange
- alert and disallow the user from having duplicate item values in the
  same select question
- alert and disallow from having duplicate question IDs as long as that
  requirement is in place (although we should probably support duplicate
  IDs by using full paths as itext ids)
Merge pull request #75 from dimagi/copy-with-numeric-item-values

change question copy naming scheme
removed unused method
moved messages into ui.js, and cleaned up
Merge branch 'master' of github.com:dimagi/Vellum into auto-height
merged with auto-height
i blame the jetlag.
Merge branch 'auto-height' into vellum-staging
leftOffset support for when window is smaller than max width and you need to scroll sideways. support for function offsets
allow negative scrolling to the left
Merge branch 'auto-height' into vellum-staging