tap.py should not be included in the product bundle since users tend to use it as a supported tool/cli instead of looking at it as a sample code

tap.py is not a supported cli command . it is intended to be looked at as an example of how you can utilize tap streams to do operations like dump or backfill but looking at number of times users have reported issues with tap.py it appears to me they like this tool and they do treat this as a supported cli.

the question in general is whether we should bundle sample scripts as part of the product or not.
my argument would be if we are shipping a tap.py which is a sample script to write a tap client in python we ca either
1- have a sample folder in the rpm and put these files under that directory
2- also ship other sample scripts ( more sdk samples , java , python ruby)