Update AI-assisted coding guidelines in CONTRIBUTING.md

[phalt]

Change description

Because it's getting way too much, man.

We need to be clearer about what is an is acceptable.

We are not here to teach people good use of LLM tooling, but we are still dealing with potentially a lot of AI miss use.

OSS and Github has fundamentally changed and there is no clear way to deal with this.

AI coding assistance disclosure

For this change, I wrote everything by hand.

Contributor check list

• I have written a description of the issue and explained why the fix solves the problem.
• I have written tests for my code changes. (NOT APPLICABLE)
• I have read and understood the AI Assisted Contribution guidelines.
• I will own this change in production, and I am prepared to fix any bugs caused by my code change.

[phalt]

I think we should add more things to this

[Naramsim]

Before commenting I'll see what some popular old open source projects are doing as well.

[phalt]

This is Ghostty's policy: https://github.com/ghostty-org/ghostty/blob/main/AI_POLICY.md

Let's find some others and compare them.

[phalt]

@Naramsim I'll get back to this when I get a free moment.

For now though, major maintainers of Python and the Python ecosystem recently had this to say about AI contributions in OSS: https://pydantic.dev/articles/pyai-oss-panel Worth reading.

[phalt]

Feedback implemented.

[Naramsim]

Is this supposed to be an HTML comment? I think it's a good idea, but the opening tag should be <!-- and the closing one -->

If we do like this the line is shown in the editor but no present in the rendered issue.

[Naramsim]

test patterns/test generation

[pokeapi-machine-user]

This Pull Request won't be deployed since the label no-deploy was found in its meta-data.