Generate gql-errors index.adoc file

[renetapopova]

No description provided.

[l-heemann]

I think we can improve how the pages are generated (especially once Neo4j has a procedure or file with all the GqlCodes) but for now the generated results look good 👍

[l-heemann]

Haven't read the code in great detail, but it looks alright from an overview.

I still consider the reliance on so many regexes a risk. But I also see no alternative to regexes unless we change to using a different data source (e.g. csv/json) which we decided against.

[l-heemann]

More of a FYI; it is possible to run one python file from another, something along the lines of

import validate-error-index
validate-error-index.main()

I like to avoid bash if I can. But I don't know what you usually do in docs, so follow whatever is standard there 🤷

[renetapopova]

I don't think we have a standard. I replaced it with python.

[neo4j-docops-agent]

Thanks for the documentation updates.

The preview documentation has now been torn down - reopening this PR will republish it.

[renetapopova]

Haven't read the code in great detail, but it looks alright from an overview.

I still consider the reliance on so many regexes a risk. But I also see no alternative to regexes unless we change to using a different data source (e.g. csv/json) which we decided against.

These scripts only generate the index file from the individual files. We'll add another check for the discrepancies between the codebase and the docs. And of course, we can still improve the approach for generating the index.adoc. at a later time.