Blueprint changes for better documentation generation

[SebastienGllmt]

Currently, documentation for Aiken projects has no good way to be generated:

• aiken docs as as command not only doesn't look great, it's also inflexible (it enforces a very specific format which makes it hard to integrate into different doc tools)
• plutus.json doesn't have enough information to be a good source for documentation generation

In Ethereum, to solve this problem, they introduced a different format called natspec that generates a JSON file (see example here). This allows any doc generation tool to parse the resulting json instead of creating a tight coupling between the compiler and the generated documentation by the compiler

Since we don't have this kind of tool for Aiken (and I'm not sure if anybody wants to spend time on this), I've instead been looking at getting code generated from plutus.json. However, it's missing the following issues:

• Currently it removes type aliases (see fr: blueprints keep type aliases #605)
• It doesn't include the relative filepath of validators (there is no way to show in the docs something like "want to see this file in more detail? Click here to see the validator code!)
• It doesn't mention utility functions (only validators) which means it's not super useful for generating docs for library packages (to some extent, this is related to Support export of functions that aren't validators #733)

It would be nice to either address these issues in plutus.json, or at least consider a separate doc output format like Ethereum did

[SebastienGllmt]

I released our tool that inspired this issue: https://twitter.com/SebastienGllmt/status/1808744947367170229

Hopefully the tool can evolve as these issues are addressed to become more generic instead of depending on Aiken-specifics