Reiterating on base data object + data manager organization

Adding formatted strings to the AppBladeDatabaseObject for “upsert”,
with a setIdFromDatabaseStatement.

Adding delete and upsert functions to the data manager.
temporarily disabling crashreportingmanager implementation of addCrashReport
for typesafety, migrating to NSNumber and NSInteger

just straight up int is bad for the compiler.
Pulling getDataManager into the private methods for the time being.

This is so we don’t have to keep on passing the buck through the
appblade singleton. Duplicate methods are clogging my style.
AppBladeDatabaseObject now has takeFreshSnapshot

for all the snapshot data.
adding data existence checking mehods to the datamanager header
Adding initWithFeedbackDictionary to the APBDatabaseFeedbackReport

should probably remove the feedback dictionary altogether and just have
a APBDatabaseFeedbackReport object instead.
Adding getCustomParams to the APBDatabaseFeedbackReport

We should pobably think of a more universal way to do this. Maybe a
helper delegate?
upsertData now alters the object passed to it, since we might need to assign an id to the object

consider rewriting this to return the new db object and it is the error
that is autoreleased. more traditional approach.
storeFeedbackDictionary now takes error:(NSError * __autoreleasing *)error as an argument. Returns the data object.