Bad interaction between prim_copyplayer and do_examine

[wyld-sw]

Copying a player via COPYPLAYER sometimes results in an object which contains properties that, when listed with examine, hangs the MUCK.

Limited testing may reveal:

• This happens when copying One, and does not seem to happen with a newly-created wizard or non-wizard player.
• This does not happen when the copied player has no properties.
• This happens with the current based and advanced, but not minimaldb (One does have a property in minimaldb).
• When the glitch happens, it appears to be attempting to list the first few properties and then starting over - causing an infinite loop.

[tanabi]

If this only happens when copying One, then maybe it is something to do with One's uniqueness and/or GOD_PRIV. We could band-aid this problem by having prim_copyplayer complain that One is unique! if you try to copy. Though that's a little bit of a cop-out, probably better to actually figure out what's wrong.