Need to validate user chosen object names more carefully

[wryun]

Smith currently checks for conflicts in its own resource names, but allows the user to set the object names in the bundle. Among other things, this means:

• two resources in the same bundle can refer to the same underlying objects, leading to Smith fighting itself if their specs are different
• users can rename the resource, but not the metadata name, which may lead to delete/recreate fight over resource
• resource creation can fail late due to ownerReference clash with object elsewhere