removed the data_files

This was causing the setup.py to try to install the files listed
For example:

running install_data
copying LICENSE.txt -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying NOTICE.txt -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying MANIFEST.in -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying setup.py -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying tox.ini -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/
copying setup.cfg -> /builddir/build/BUILDROOT/python-pyvmomi-5.5.0.2014.1.1-1.fc20.x86_64/usr/

Those files should not go in that location.
The MANIFEST.in file does enough by adding those files to the sdist
from there if you intend to have those files installed by setup.py
you should tell it where to put them. This change allows packagers
to specify where those files end up in their packaging process.
removed the shebang from the top of a few files

The #!/usr/bin/env python should be used for scripts
not for module files. This causes rpmlint to get angry
about files being non executable. For example:

python-pyvmomi.noarch: E: non-executable-script /usr/lib/python2.7/site-packages/pyVmomi/ManagedMethodExecutorHelper.py 0644L /usr/bin/env
python-pyvmomi.noarch: E: non-executable-script /usr/lib/python2.7/site-packages/pyVmomi/Iso8601.py 0644L /usr/bin/env
python-pyvmomi.noarch: E: non-executable-script /usr/lib/python2.7/site-packages/pyVmomi/DynamicTypeManagerHelper.py 0644L /usr/bin/env

This change fixes that problem.
Merge pull request #149 from michaelrice/rpm_fixes

Rpm fixes