The statvfs() call depends on the underlying filesystem
supporting this.  On RTEMS, the IMFS filesystem type
does not, and it returns the ENOSYS errno.  This is better
translated to OS_ERR_NOT_IMPLEMENTED rather than OS_ERROR.

Rather than relying on the BSP to preallocate, the ram disk
block devices can be created based on request.  This correlates
with the way RAM disks are implemented on VxWorks and is
cleaner and more flexible by making it more independent
of the BSP.

This string should be of OS_FS_DEV_NAME_LEN

This provides a better method of handling test abort,
in a BSP-specific manner.

Remove the OS_VolumeTable definition from all BSPs, but provide
a default (empty) one to support linking when OMIT_DEPRECATED is
not set.

Do not assume BSP volume table provides a "/cf" directory map.
Instead, create a UT-specific map of a consistent name, and use
that.

Add a distinct type for FS_BASED entries, and an UNKNOWN value
for when a type is actually not yet identified.

This can be used to identify the FS type first at the shared
layer, then in the implementation layer as a fallback option
if not identifiable in the shared layer.

Use the volume name prefix "RAM" as a hint that the volume
is supposed to be a VOLATILE disk as opposed to a normal disk.
This is done in shared layer so it applies to all OS types.

Confirm that the "selectable" flag is set before
calling the underlying select() API.

Also update unit tests to match.

If the "OSAL_EXT_SOURCE_DIR" cache variable is set, this location
will be checked first for a BSP/OS implementation layer.  This can
point to an out-of-tree implementation layer if necessary.

However it is discouraged from actually doing this as there is no
attempt at API stability at the low level implementation layer.

Implement OS_GetResourceName, OS_ForEachObjectByType

Corrects issue when a task waiting on a binary semaphore is
deleted, it left the mutex in a locked state preventing other
tasks from using the mutex.

The mutex to protect the timer callback (timecb) resource table
was missing.

Add a wrapper at the shared layer to provide a common location
to check the status of global lock/unlock ops.

All calls to OS_Lock_Global_Impl and OS_Unlock_Global_Impl from
the shared modules are replaced with calls to this wrapper.

… between 0 and <MAX and output array indices vary

Fix #455, correct length of device_name in filesys

Fix #474, Add timecb global mutex

Fix #293, Expand API for object queries

Fix #450, add external source directory for OS/BSP

Fix #470, Binary sem task delete issues

Fix #447, Resolve doxygen warnings

Fix #459, dynamically create RAM disk devices on RTEMS

Fix #457, provide BSP shutdown handler

Fix #454, Better error translation on statvfs()

…sing-Tests

Fix #374, Add Object Utility API functional tests

…ssing-Functional-API-Tests

Hotfix #374 object utilitys missing functional api tests

Fix #476, add global lock/unlock wrapper

Use "object_id" rather than "id" for consistency with other API calls.
The difference was flagged as a warning by doxygen.

- Correct merge issue with regards to the OS_Global_Unlock function
- Correct use of OS_TaskGetId() - need to use Impl variant here.

Fix #367, 453, 456, 460, Deprecate OS_VolumeTable and other fixes