opal/accelerator: Initial accelerator framework implementation

Add new accelerator framework. The component selection logic makes
the assumption that there will only be 1 valid accelerator per
instance. It will return the NULL/no-op Component if no components can be found,
to allow fast execution path to not perform extra checks. It will also fail
initialization if multiple accelerators are successfully initialized

Added NULL Component to the Accelerator framework which does no-ops.
This will allow Accelerator selection logic to always succeed and get
rid of extra if checks on the critical execution path (because Accelerator
will always exist).

Signed-off-by: William Zhang <wilzhang@amazon.com>
Co-authored-by: William Zhang <wilzhang@amazon.com>
Co-authored-by: Seth Zegelstein <szegel@amazon.com>
Signed-off-by: William Zhang <wilzhang@amazon.com>

Author: wckzhang

opal/mca/accelerator/Makefile.am

@@ -0,0 +1,29 @@
+#
+# Copyright (c) 2014      Intel, Inc.  All rights reserved.
+# Copyright (c) 2022      Amazon.com, Inc. or its affiliates.
+#                         All Rights reserved.
+# $COPYRIGHT$
+#
+# Additional copyrights may follow
+#
+# $HEADER$
+#
+
+# main library setup
+noinst_LTLIBRARIES = libmca_accelerator.la
+libmca_accelerator_la_SOURCES =
+
+# local files
+headers = accelerator.h
+libmca_accelerator_la_SOURCES += $(headers)
+
+# Conditionally install the header files
+if WANT_INSTALL_HEADERS
+opaldir = $(opalincludedir)/$(subdir)
+nobase_opal_HEADERS = $(headers)
+endif
+
+include base/Makefile.am
+
+distclean-local:
+	rm -f base/static-components.h