add --requirements option to deploy and write-manifest

[amol-]

soometimes the user might have requirements specified in a file that is not the default requirements.txt file, for example it might be requirements.txt.lock which is what connect uses and fetches if content get-lockfile command is used to fetch connect lockfile.

Having a --requirements FILENAME option would allow the user to explicitly point the deploy process to such file