Add database schema management using Alembic

This patch replaces contrib/realtime/ with a new setup for managing the
database schema required for database integration with Asterisk.  In
addition to initializing a database with the proper schema, alembic can do a
database migration to assist with upgrading Asterisk in the future.
Hopefully this helps make setting up and operating Asterisk with a database
easier.

With this the schema only needs to be maintained in one place instead of
once per database.  The schemas I have added here have a bit of improvement
over the examples that were there before (some added consistency and added
some missing indexes).  Managing the schema in one place here also applies
to all databases supported by SQLAlchemy.

See contrib/ast-db-manage/README.md for more details.

Review: https://reviewboard.asterisk.org/r/2731

patch by Russell Bryant (license 6300)



git-svn-id: https://origsvn.digium.com/svn/asterisk/branches/12@397874 65c4cc65-6c06-0410-ace0-fbb531ad65f3

contrib/realtime/mysql/voicemail_data.sql

@@ -1,29 +0,0 @@
-DROP TABLE IF EXISTS voicemail_data;
-CREATE TABLE voicemail_data (
-	-- Path to the recording
-	filename CHAR(255) NOT NULL PRIMARY KEY,
-	-- Mailbox number (without context)
-	origmailbox CHAR(80),
-	-- Dialplan context
-	context CHAR(80),
-	-- Dialplan context, if voicemail was invoked from a macro
-	macrocontext CHAR(80),
-	-- Dialplan extension
-	exten CHAR(80),
-	-- Dialplan priority
-	priority INT(5),
-	-- Name of the channel, when message was left
-	callerchan CHAR(80),
-	-- CallerID on the channel, when message was left
-	callerid CHAR(80),
-	-- Contrary to the name, origdate is a full datetime, in localized format
-	origdate CHAR(30),
-	-- Same date as origdate, but in Unixtime
-	origtime INT(11),
-	-- Value of the channel variable VM_CATEGORY, if set
-	category CHAR(30),
-	-- Length of the message, in seconds
-	duration INT(11)
-);
-
-