Per our discussion, I think we decided that we don't need the chef_object:rename_supported callback. We can unify the endpoint behavior w.r.t. returning 201 on rename and let resources opt-out of supporting rename entirely by failing to validate when URL doesn't match JSON body.