Added extensions for virtual environments in .gitignore

[varuntotakura]

Description

.gitigore doesn't have anything about environments in its extensions.

When we try to use a virtual environment to run the whole package locally, if we try to add the files to the repository, the environment files are also being added.

To fix that I have included extensions of the virtual environments

Checklist

• Follows official PR format
• New features are properly documented (with an example if appropriate)
• Changes are listed in changelog

---

📚 Documentation preview 📚: https://arviz--2372.org.readthedocs.build/en/2372/

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.01%. Comparing base (8795992) to head (90c4e75).
Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2372   +/-   ##
=======================================
  Coverage   87.01%   87.01%           
=======================================
  Files         124      124           
  Lines       12788    12788           
=======================================
  Hits        11128    11128           
  Misses       1660     1660           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[tomicapretto]

Other options that come to my mind are

• hatch.toml
• pdm.lock
• Pipfile.lock
• Pipfile
• poetry.lock`

I'm not completely sure if people should be building ArviZ following an approach different from the recommended one, but people can do whatever they want so it's probably good to have these files/directories listed.

[varuntotakura]

Yes, I believe it's important to use the recommended approaches. However, when installing dependencies, some may prefer to use a virtual environment. While it’s important to track the core dependency and configuration files like Pipfile, Pipfile.lock, poetry.lock, pdm.lock, and hatch.toml in version control, it’s equally important to ignore files and directories that are specific to individual developers' environments, such as virtual environments. These files are not relevant to other people's builds and can clutter the repository.

[amaloney]

If you're looking to

...ignore files and directories that are specific to individual developers' environments...

then you may want to add items you want git to ignore from your personal setup in the file .git/info/exclude. This way you can ignore what ever you want, and we would not have to keep track of the most recent flavor of things to ignore when building an environment in the .gitignore file.

I'm not opposed to the addition of the .env as this is typically where people will store credentials for an app they are using, and use something like python-dotenv to read those credentials, but the others are not necessary in my opinion. Especially when there are mechanisms for local ignores when using git, and you can cherry pick new/updated files via the command line without running a git add *, which can be dangerous if you have dotfiles with credentials stored in them.