Remove possibility to use sqlite

It's known to be broken, and there was agreement to only use the
database barclamp.

This means we can remove the whole database_engine dance, which
simplifies things.
Remove attributes that exist only because of copy&paste from keystone
Do not hardcode admin tenant
Fix creation of /etc/sudoers.d/quantum-rootwrap

It's not needed on SUSE (our package have this already) and the user
should not be hardcoded.
Fix typo
Install quantum packages before doing anything else

We need the basic quantum packages to have quantum-rootwrap and the
quantum services installed, before we do the rest. Otherwise, the first
chef-client run will fail because other recipe will try to access these
resources that don't exist yet.

Example of failure:

[Sun, 16 Jun 2013 13:13:57 +0000] INFO: Processing service[openstack-quantum]
action restart (quantum::server line 186)

================================================================================
Error executing action `restart` on resource 'service[openstack-quantum]'
================================================================================

Mixlib::ShellOut::ShellCommandFailed
------------------------------------
Expected process to exit with [0], but received '1'
---- Begin output of /sbin/service openstack-quantum restart ----
STDOUT:
STDERR: service: no such service openstack-quantum
---- End output of /sbin/service openstack-quantum restart ----
Ran /sbin/service openstack-quantum restart returned 1
Respect debug attribute in all config files
Do not make quantum.conf world-readable

It contains passwords.
Do not hardcode API port when registering endpoint

We have an attribute to set it.
Have a default path for quantum-rootwrap

Finding the path to quantum-rootwrap in a ruby_block makes
node[:quantum][:rootwrap] exist too late to be used when populating
quantum.conf in the first chef-client run. This results in some failures
to use sudo, which are not critical but annoying.

Instead of proceeding this way we just default the path to
quantum-rootwrap to /usr/bin/quantum-rootwrap (correct path for
upstream, Ubuntu and SUSE), and keep the ruby_block to fix the path if
it's not the same. Things will still fail in the first chef-client run
if it's not the right path, but chef convergence will make it work for
later runs. And it now works directly in the first run in most cases.
Merge pull request #61 from cdearborn/pull-req-release-mesa-1.6-master-c12fdbce5ffe0873f4dc4fba7cbf31343b41d699

https://github.com/crowbar/barclamp-quantum/pull/61

Merged by devtool for cloudsleuth