pin uaa-customized to what the manifest generates for staging

[cweibel]

Changes proposed in this pull request:

• Removes using the uaa-customized version using in the bosh-deployment resource which takes a higher precedence over what is generated by the ops files. For staging, I want what is in the ops file, not the concourse resource, to correspond with pinning staging to uaa v78.
• Remove of this block will revert to the version used/managed by the pipeline
• Part of https://github.com/cloud-gov/private/issues/2747

security considerations

Part of eventually using the v78 line of uaa