/features endpoint relies on metadata from manifest that might not be available

I guess this will require a judgement call. The problem is that FeaturesEndpoint relies on this snippet:

	private void addFeature(Features features, NamedFeature feature) {
		Class<?> type = feature.getType();
		features.getEnabled()
				.add(new Feature(feature.getName(), type.getCanonicalName(),
						type.getPackage().getImplementationVersion(),
						type.getPackage().getImplementationVendor()));
	}

and the package information from the manifest is not available in general (in particular not in a GraalVM native image). It would be ideal to provide a fallback. Or just omit it if not known?

Start by locating FeaturesEndpoint and its addFeature method, then inspect how NamedFeature metadata is obtained and how the /features response is tested. Reproduce the missing manifest package information, including the GraalVM native-image case, and agree whether unknown version and vendor data should use a fallback or be omitted. Done means the chosen behavior is covered by tests.