feat: Update AutoMod implementation

[TheEnigmaBlade]

Summary

Since the original implementation of the AutoMod API (during the AutoMod beta), the API has been repeatedly changed. This pull request changes the following:

• Adds the trigger type (rule_trigger_type) to AutoModActionExecutionEvent, which seems to have been forgotten.
• Adds newer properties to AutoMod trigger metadata (ex. regex_patterns, allow_list).
• Adds the mention_spam trigger type enum value.
• Removes the harmful_link enum value from AutoModTriggerType, as Discord merged the filter with spam early in the beta.
• Updates the documentation to include all AutoMod classes and enums, along with the updates above.

I apologize about the improper commit messages, as I read the guidelines 3 months too late.

Information

• This PR fixes an issue.
• This PR adds something new (e.g. new method or parameters).
• This PR is a breaking change (e.g. methods or parameters removed/renamed).
• This PR is not a code change (e.g. documentation, README, typehinting,
  examples, ...).

Checklist

• I have searched the open pull requests for duplicates.
• If code changes were made then they have been tested.
  • I have updated the documentation to reflect the changes.
• If type: ignore comments were used, a comment is also left explaining why.

[BobDotCom]

In addition to the other comments, please add a changelog entry for all of the changes here

[TheEnigmaBlade]

All requested changes have been applied.

[plun1331]

• Removes the harmful_link enum value from AutoModTriggerType, as Discord merged the filter with spam early in the beta.

This change doesn't seem to have been made, and instead of removing it we could instead deprecate it and alias it for spam

[BobDotCom]

I apologize about the improper commit messages, as I read the guidelines 3 months too late.

FWIW, your commit messages are fine. We use squash merges for PRs, only the PR title matters.

[TheEnigmaBlade]

• Removes the harmful_link enum value from AutoModTriggerType, as Discord merged the filter with spam early in the beta.

This change doesn't seem to have been made, and instead of removing it we could instead deprecate it and alias it for spam

The removal was reverted by @Lulalaby a little earlier, which is fine. Deprecation without aliasing would probably be best to avoid breaking changes, as aliasing harmful_link to spam could cause existing usages to double-process the same spam event (ex. actioning a user twice; logging twice). That could be considered a breaking change in my eyes.

I added the property to the docs for AllowModTriggerType (since it didn't exist before) with a deprecated message. Is that fine?

[BobDotCom]

The removal was reverted by @Lulalaby a little earlier, which is fine. Deprecation without aliasing would probably be best to avoid breaking changes, as aliasing harmful_link to spam could cause existing usages to double-process the same spam event (ex. actioning a user twice; logging twice). That could be considered a breaking change in my eyes.

I added the property to the docs for AllowModTriggerType (since it didn't exist before) with a deprecated message. Is that fine?

I actually think it should be removed, considering it's not on the api docs https://discord.com/developers/docs/resources/auto-moderation#auto-moderation-rule-object-trigger-types.

@Lulalaby @plun1331 opinions?

[Lulalaby]

It's still existing, some bots might encounter it, that's why I reverted the removal again

[TheEnigmaBlade]

According to the Discord staff I've talked to previously, the harmful link filter is permanently removed in favor of the spam filter. It only existed during the early beta tests and has not been public, so it would be impossible for a bot to ever receive such an event.

[codecov]

Codecov Report

Merging #1809 (906cd9f) into master (b5f4b91) will decrease coverage by 0.02%.
The diff coverage is 15.78%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1809      +/-   ##
==========================================
- Coverage   33.21%   33.18%   -0.03%     
==========================================
  Files          96       96              
  Lines       18657    18674      +17     
==========================================
+ Hits         6196     6197       +1     
- Misses      12461    12477      +16     

Flag	Coverage Δ
macos-latest-3.10	33.16% <15.78%> (-0.03%)	⬇️
macos-latest-3.11	33.16% <15.78%> (-0.03%)	⬇️
macos-latest-3.8	33.18% <15.78%> (-0.03%)	⬇️
macos-latest-3.9	33.18% <15.78%> (-0.03%)	⬇️
ubuntu-latest-3.10	33.16% <15.78%> (-0.03%)	⬇️
ubuntu-latest-3.11	33.16% <15.78%> (-0.03%)	⬇️
ubuntu-latest-3.8	33.18% <15.78%> (-0.03%)	⬇️
ubuntu-latest-3.9	33.18% <15.78%> (-0.03%)	⬇️
windows-latest-3.10	33.16% <15.78%> (-0.03%)	⬇️
windows-latest-3.11	33.16% <15.78%> (-0.03%)	⬇️
windows-latest-3.8	33.18% <15.78%> (-0.03%)	⬇️
windows-latest-3.9	33.18% <15.78%> (-0.03%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files	Coverage Δ
discord/automod.py	28.83% <6.25%> (-2.93%)	⬇️
discord/raw_models.py	28.10% <50.00%> (-0.19%)	⬇️
discord/enums.py	78.75% <100.00%> (+0.03%)	⬆️

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b5f4b91...906cd9f. Read the comment docs.

.