Apply doc changes for bsls::TimeUtil::initialize
First pass at cleanup for bdeverify

Currently there are still around 6400 warnings, although a large number
of these should resolve as false positives in a new iteration of
bdeverify in a few days.  Another large set are repeated warnings
about a lack of documentation each time a template is instantiated
and while these must be addressed, it will be easier to see and
address such issues once the false-positives are eliminated.
mend
Hashtable cleanups from bdeverify
mend
Unbreak the dev-integration build

Previously tried to satisfy bde_verify alloctor-propogation issues by
providing a partial specialization of 'bslma::UsesBslmaAllocator' for an
implementation class nested inside the 'HashTable' template.  Unfortunately
this is not valid C++ syntax, so apply the nested trait idiom instead,
where the primary template can deduce the correct behavior without
requiring an additional specialization.
Further bde_verify updates for hash tables

This takes a proper attempt at cleaning up the bde_verify issues associated
with trying to flag allocator usage for a nested class within a class
template.

This fix moves the nested class outside the primary class template, which
solves a number of isses.  Ths documentation is now more conventional,
the nested trait problems go away, and we no longer need to work around
the MSVC bug that did not recognize the out-of-line definitions of the
methods of a nested class (in a class template).
Apply phabricator feedback to hash table
More review comments from Hyman
Fix IBM compiler check in test driver

The XLC 12 compiler fixes the bug we are working around in
this test driver.  Unfortunately, we tested based on the
OS platform rather than the compiler, but the version check
is still simple to correct.
Fix banners in array-primitives test driver

First pass fixing bde_verify warnings:
This pass fixes up banners and standard test driver macros.
Formatting fixes in array-prmitives, phase 2

This pass fixes three sets of warnings:
declarations/headers appear in the correct order
make appropriate use of line-wrap
minor issues with template declarations
Formatting fixes in array-prmitives, phase 3

This phase correctly annotates early returns statements and
marks up single argument constructors as either 'explicit'
or // IMPLICIT.
Formatting fixes in array-prmitives, phase 4

Confirm that the functions declared as Tested in each test case
match those declared in the component level test plan.  Fixing
this turned up two concerns that should be verified at a later
date:
1)  Many of the tested signatures did not match, mostly differing
    in parameter order.  Generally we believe the correct order
    must be tested, as this component has a strong pedigree in
    production, but it is concerning in cases where the types
    are the same, and only the parameter names indicate purpose.
2)  A couple of functions in the header are now clearly not
    tested - 'defaultConstruct' and 'emplace'.
Formatting fixes in array-prmitives, phase 5

Fix up some (but far from all) missing documentation for function
level contracts in the test driver.
Clean up bde_verify markup

This final patch of the sequence removes the bde_verify pragmas used to silence
distracting warnings that will need more effort to fix - we still want to see
those warnings to prompt us to fix such issues in the future.
Fix IBM version check

The IBM version number is in hex, so version 12 is represented by
0x0c, rather than 0x12.
removed unused (and bogus) [BEGIN|END]_BSLX_EXCEPTION_TEST macros
Fixed numerous bdeverify warnings.

BDE's bdeverify tool flagged several non-normative style warnings
on the decimal components.  This is expected, due to their
original exogeny.  The most egregious warnings are fixed in this
change.
Added a necessary include for decNumber dependency.

There are forwarding functions to decNumber functionality in
bdldfp_decimalutil.  These functions need to include the
requisite 'bdl+decnumber' header, such that they will properly
compile.  The original source of the decNumber implementation
names was a transitive include dependency from
'bdldfp_decimalimplutil.h'.

This should allow the various quanta (and other) functions in
'bdldfp::DecimalUtil', which rely upon 'bdl+decnumber' to
compile, even when IBM hardware modes are enabled.