Installation scripts for daemon mode on Ubuntu using Upstart

This work is based upon upstream work in bitcoin core on the master branch and in some PRs.
The "Cherry Pick" commit is here: https://github.com/msgilligan/mastercore/commit/55a97b93223919171195fb11c11281c9cdb0be3e

All files (both the "cherry pick" files and the ones that I've added are in the `contrib` subdirectory.


Maybe this is already clear, but just to be sure some background information which might be handy to know: there is a difference between `min-X-fee` and `X-fee`. The `min-X-fee` defines the absolute minimum whereby the `X-fee` is never less than the `min-X-fee`. The hardcoded default is overwritten by a config value. To be more specific: there is the `mintxfee` which is either defined by the client's hardcoded default or config/startup arguments and there is the `paytxfee` which can be set via config/startup as well, but also on the fly via RPC command `settxfee`. The actual fee is `max(mintxfee, paytxfee)`. The relayTxFee has a hardcoded default and can be set via config/startup arguments, too. - Unfortunally there is no RPC call to change this value on the fly.

Related to `nMinRelayTxFee`: at the beginning a [magic number](https://github.com/mastercoin-MSC/mastercore/blob/426592e287f79b37fbdddb5cad14ce9bf2ca1317/src/mastercore.h#L33) was used for all output amounts and this number was changed from time to time to identify and differentiate between clients and versions. This is currently done with Omni as well and you can identify transactions that are created by Omni on it's output amounts of 0.00005757. [Switching to an approach](https://github.com/mastercoin-MSC/mastercore/pull/110) which yields output amounts derived from script length and based on minRelayTxFee sort of [killed the ability to "tag" clients](https://github.com/mastercoin-MSC/mastercore/pull/66#issuecomment-51079112), but I later realized it's still possible, even without static magic number. I used 1001 basically to make my point and suggested to change this number, if a new "tag" is required.

Given how the `nMinRelayTxFee` is [ab]used for client identification purposes, I think commenting the line in `bitcoin.conf` is the way to go at the moment.