config_object_error log should not assume a request context always present

[Hampapur Ajay]

If there is a db entry that is not in correct state, following traceback is observed on startup of api-server

The above is a description of an error in a Python program. Here is
the original traceback:

Traceback (most recent call last):
  File "/usr/lib/python2.7/dist-packages/vnc_cfg_api_server/vnc_cfg_ifmap.py", line 959, in walk
    result = fn(obj_type, uuid_list)
  File "/usr/lib/python2.7/dist-packages/vnc_cfg_api_server/vnc_cfg_ifmap.py", line 1553, in _dbe_resync
    obj_uuid, None, obj_type, 'dbe_resync:ifmap_alloc', str(e))
  File "/usr/lib/python2.7/dist-packages/vnc_cfg_api_server/vnc_cfg_ifmap.py", line 1978, in config_object_error
    id, fq_name_str, obj_type, operation, err_str)
  File "/usr/lib/python2.7/dist-packages/vnc_cfg_api_server/vnc_cfg_api_server.py", line 2360, in config_object_error
    self._set_api_audit_info(apiConfig)
  File "/usr/lib/python2.7/dist-packages/vnc_cfg_api_server/vnc_cfg_api_server.py", line 2372, in _set_api_audit_info
    apiConfig.url = get_request().url
  File "/usr/lib/python2.7/dist-packages/vnc_cfg_api_server/context.py", line 77, in get_request
    return gevent.getcurrent().api_context.request
AttributeError: 'greenlet.greenlet' object has no attribute 'api_context'