Ignoring Berksfile.lock

I don't think we want to include a Berksfile.lock for att-cloud
maintained cookbooks.  Mostly b/c it contains path info local
to the user that ran `berks`.