OpenBMCManager: fix v1_1_0.Manager BaseType

The OpenBMCManager.v1_1_0.Manager ComplexType was inheriting from
Resource.OemObject instead of OpenBMCManager.v1_0_0.Manager,
silently dropping all v1_0_0 properties including the Certificates
NavigationProperty from the schema. This was causing the bmcweb bumps
to fail.

As explained to me, because openbmc_managers.hpp emits
"@odata.type": "#OpenBMCManager.v1_1_0.Manager" at runtime, the
Redfish Service Validator resolves every Oem/OpenBmc property against
that type. With Certificates absent from the type definition, the RSV
raised an Unknown Property Error on
Oem/OpenBmc/Certificates.

Fix the BaseType to OpenBMCManager.v1_0_0.Manager so v1_1_0 inherits
Certificates and any other v1_0_0. This is the standard CSDL versioning
pattern.

This was introduced by 762a74183 [1].

[1]: https://gerrit.openbmc.org/c/openbmc/bmcweb/+/85785.

Tested: Inspection only.

Change-Id: I95b8a27f1b3b86192c34f61fb3a48d2d42a4df6d
Signed-off-by: Gunnar Mills <gmills@us.ibm.com>