fix: Command Auto Syncing

[Icebluewolf]

Summary

This is very much a draft and needs lots of testing. I just want to put it somewhere public so that I can get eyes on it.
This is something I am not quite sure how to cleanly fix at the moment.

TODO: Change the below default if needed to use the correct default integration types and contexts

I also need to check what the behavior is for undocumented fields in the payload from discord that may be added in the future. I believe the best option is to ignore those fields.
This gist (https://gist.github.com/Icebluewolf/1842ea5f7234ba40e5df18191bb135a0) contains 2 files. The first is where I developed the fix so that I did not have to make real API calls and is here for reference if someone wants to do the same. The second is unit tests for the new system. Both are very rough and messy sorry 🙃. This change needs to be tested extensively, so if someone sees test cases I missed or more test cases that should be added please let me know.

This PR attempts to fix the long running issue with the application command auto-syncing system. Currently the system is over eager and preforms upserts on commands that do not need to be updated. The main culprit is incorrect default value checking. This PR implements a more robust and easily extendable comparison system for commands.

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.
• I have updated the changelog to include these changes.

[pycord-app]

Thanks for opening this pull request!
Please make sure you have read the Contributing Guidelines and Code of Conduct.

This pull request can be checked-out with:

git fetch origin pull/2990/head:pr-2990
git checkout pr-2990

This pull request can be installed with:

pip install git+https://github.com/Pycord-Development/pycord@refs/pull/2990/head

[Paillat-dev]

@Icebluewolf Feel free to mark this as ready for review once you think it is ready, note the linter failing in the gh actions

[Paillat-dev]

Do you think that #1745 could be addressed here as well ?

[Icebluewolf]

I updated the gist in the description to include a test file [test_command_syncing2.py](https://gist.github.com/Icebluewolf/1842ea5f7234ba40e5df18191bb135a0#file-test_command_syncing2-py). This test suite works with the current implementation in the library. I believe this is enough refactoring for one PR but I might make another PR to clean up the other parts of syncing. The only concern I have left is the default value for installation contexts as this changes depending on what is selected in the dev portal.

I do expect to do some cleanup tasks as well

[Paillat-dev]

Could we fetch our app info and then fill it based on that ? See @Lumabots 's appinfo PR. Or would that not work ?

[Icebluewolf]

Do we get app info before on_connect is called? Also that PR is not merged yet so this would have to wait.

[Paillat-dev]

We don't but we could if this requires it

[Icebluewolf]

I have not done extensive testing with sub commands, sub sub commands, and if Discord gives extra information that we dont care about (aka not implemented) in the payload.

[Icebluewolf]

Updated my tests in the gist again. This should be fully functional now except for integration types. I believe contexts does not need special casing like I previously thought.