feat: Support for registering new Artifact Types

[ivangsa]

Feature or Problem Description

I would like to be able to register new ArtifactType/s to apicurio-registry.

I have different use cases for this:

• register plaintext or markdown files as artifacts. Some groups contains different artifacts openapi, asyncapi and avros, I would like to register i.e. README.md with info about those artifacts both for users/developers as well as context for LLMs for agentic programing, and having those instructions along with the artifacts themselves
• register json/yaml files different to valid openapi, asyncapi ymls. Use cases for this are many: registering referenciable chunks that are not complete APIs (and do not validate as apis), register a services.yml that represents relationships consumer/producer and would be nice to have them registered and versioned in the registry
• register ZenWave Domain Language .zdl files which represent bounded context and can reference apis. It would be great have them registered as structured artifacts with refs, but can work as plaintext files for first versions

Proposed Solution

• allow register plaintext files
• allow register json/yaml artifacts types

for later versions:

• allow register zdl files as structured artifacts

Additional Context

[carlesarnal]

Hello @ivangsa,

Have you checked the blog post here? It should fit your needs.

[ivangsa]

I'm reading it now, it may work..
I will need to dig into creating a sample project and adding some custom types

I wonder if it would be posible to add custom artifact types with java classes (not scripts) without doing a custom build, or Quarkus AOT compalation would prevent this alltogether

because for complex custom types like the zdl, I'm not sure how the prerformace would be to pack the parser and everythihng as nodejs script..