Stop using deprecated pydantic config class and filter gradio warnings from tests

[freddyaboulton]

Description

We're using a deprecated pydantic api (https://docs.pydantic.dev/2.5/migration/#changes-to-config) so migrating to the new api.

In addition, warnings raised by our own code (gr.LogoutButton, etc) are clogging up the pytest warning log which makes it hard to review/see legit warnings. These warnings are usually raised because we're testing an API we've deprecated but not removed.

🎯 PRs Should Target Issues

Before your create a PR, please check to see if there is an existing issue for this change. If not, please create an issue before you create this PR, unless the fix is very small.

Not adhering to this guideline will result in the PR being closed.

Tests

1. PRs will only be merged if tests pass on CI. To run the tests locally, please set up your Gradio environment locally and run the tests: bash scripts/run_all_tests.sh

2. You may need to run the linters: bash scripts/format_backend.sh and bash scripts/format_frontend.sh

[gradio-pr-bot]

🪼 branch checks and previews

•	Name	Status	URL
	Spaces	building...
	Website	ready!	Website preview
🦄	Changes	detected!	Details

[gradio-pr-bot]

🦄 change detected

This Pull Request includes changes to the following packages.

Package	Version
gradio	patch

• Maintainers can select this checkbox to manually select packages to update.

With the following changelog entry.

Stop using deprecated pydantic config class and filter gradio warnings from tests

Maintainers or the PR author can modify the PR title to modify this entry.

Something isn't right?

• Maintainers can change the version label to modify the version bump.
• If the bot has failed to detect any changes, or if this pull request needs to update multiple packages to different versions or requires a more comprehensive changelog entry, maintainers can update the changelog file directly.

[abidlabs]

cool thanks @freddyaboulton!

[freddyaboulton]

Thanks @abidlabs !