Catch BESError in HDF5RequestHandler dap methods.

[ndp-opendap]

This branch fixes the following issue. In the HDF5RequestHandler the DAP response methods utilize a top level try block and the following catch pattern:

    catch(InternalErr & e) {
        throw BESDapError(e.get_error_message(), true, e.get_error_code(),
                       __FILE__, __LINE__);
    }
    catch(Error & e) {
        throw BESDapError(e.get_error_message(), false, e.get_error_code(),
                       __FILE__, __LINE__);
    }
    catch(...) {
        string s = "unknown exception caught building HDF5 DataDDS";
        throw BESInternalFatalError(s, __FILE__, __LINE__);
    }

This is problematic because the code being run throws various children of BESError, these errors are being swept up in the (...) clause and turned into BESInternalFatalErrors even when they are not fatal errors. Adding this solves the problem nicely:

    catch(BESError & e) {
        BESDEBUG(HDF5_NAME, "Caught BESError! Message: " << e.get_message() << endl);
        throw;
    }

The affected methods are:

• HDF5RequestHandler::hdf5_build_das()
• HDF5RequestHandler::hdf5_build_data()
• HDF5RequestHandler:: hdf5_build_data_with_IDs()
• HDF5RequestHandler::hdf5_build_dds()
• HDF5RequestHandler::hdf5_build_dmr()
• HDF5RequestHandler::hdf5_build_dmr_with_IDs()

[jgallagher59701]

OK, merge this. But see my PR on libdap that affects libdap::Error and the file/line info.