Update installed files to latest

As a comment in https://gerrit.openbmc.org/c/openbmc/bmcweb/+/74159
pointed out, although 74159 fixed the link, it didn't rename the file to
the latest. It seems rea

Update installed files to latest

As a comment in https://gerrit.openbmc.org/c/openbmc/bmcweb/+/74159
pointed out, although 74159 fixed the link, it didn't rename the file to
the latest. It seems reasonable we do that.

Probably should have been in 74159, i was impatient. Even though
74159 was really simple, still should have waited.

Tested:
```
head -n 4 redfish-core/schema/dmtf/json-schema-installed/Certificate.v1_*.json
{
"$id": "http://redfish.dmtf.org/schemas/v1/Certificate.v1_8_3.json",
"$ref": "#/definitions/Certificate",
"$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",

```
```
ls redfish-core/schema/dmtf/json-schema-installed/Certificate.v1_*.json

redfish-core/schema/dmtf/json-schema-installed/Certificate.v1_8_3.json
```

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

show more ...

Update symlinks for 2024.2

Wrote a quick bash script to update these symlinks.

These are versioned out in json schema directory[1].

The symlinks don't work without this update.

[1]: https://githu

Update symlinks for 2024.2

Wrote a quick bash script to update these symlinks.

These are versioned out in json schema directory[1].

The symlinks don't work without this update.

[1]: https://github.com/openbmc/bmcweb/tree/master/redfish-core/schema/dmtf/json-schema

28cfceb2980baa76d7f0599dd4a331ceaec52e1f pulled in 2024.2

Tested: Cat a few of these links. They appear to work.

Before:
```
head -n 4 redfish-core/schema/dmtf/json-schema-installed/Certificate.v1_*.json
head: cannot open
'redfish-core/schema/dmtf/json-schema-installed/Certificate.v1_8_2.json'
for reading: No such file or directory
```

After:
```
head -n 4 redfish-core/schema/dmtf/json-schema-installed/Certificate.v1_*.json
{
"$id": "http://redfish.dmtf.org/schemas/v1/Certificate.v1_8_3.json",
"$ref": "#/definitions/Certificate",
"$schema": "http://redfish.dmtf.org/schemas/v1/redfish-schema-v1.json",
```

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

show more ...

Make schemas selectable

Which schemas are installed should be selectable in both a meson config,
and trivially by forks. This commit gets us closer to that idea.

It does it in several ways, first,

Make schemas selectable

Which schemas are installed should be selectable in both a meson config,
and trivially by forks. This commit gets us closer to that idea.

It does it in several ways, first, the code for generating
JsonSchemaFile resources has been changed to be generated at runtime,
based on files on disk. This is slightly slower, but allows installing
schemas from anywhere, and matches the CSDL handling.

Next, the schema folders are separated into two sets
csdl -> This includes the complete schema pack from dmtf
installed -> this includes only the schemas the bmc includes

Similar folders exist for json-schema and json-schema-installed.

This allows any additional schemas to be a single symlink addition.
Note, this also checks in all of the dmtf json schemas, not just the
versions we use. This allows us to update the schema pack without
needing to break our versions we ship.

Because the static files are now selectable, all files need to be in a
folder. This forces the css and image for the redfish built-in gui to
be moved.

Tested:
/redfish/v1/JsonSchemas returns the correct result
/redfish/v1/JsonSchemas/UpdateService returns a JsonSchemaFile instance
/redfish/v1/JsonSchemas/UpdateService/UpdateService<version>json returns
the JsonSchemaFile contents.

Redfish service validator passes.

Change-Id: Ie96b2e4b623788dc2ec94eb40fcfd80325f0d826
Signed-off-by: Ed Tanous <ed@tanous.net>

show more ...