Deprecate the global Viper instance

[sagikazarmark]

Preflight Checklist

• I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description

There is a global, singleton instance in Viper.

Although it makes cross-package configuration easy, it became clear that it's more a burden not just from a maintenance perspective:

• Moving away from the setter-pattern has been challenging
• Testing is harder with the global instance
• Concurrent or subsequent changes may lead to unexpected behavior in a way that's nearly impossible to debug with the global instance

Proposed Solution

Deprecate the global instance. Remove it in v2.

Alternatives Considered

Provide an alternative package for people who want to continue using it.

Additional Information

No response

[github-actions]

👋 Thanks for reporting!

A maintainer will take a look at your issue shortly. 👀

In the meantime: We are working on Viper v2 and we would love to hear your thoughts about what you like or don't like about Viper, so we can improve or fix those issues.

⏰ If you have a couple minutes, please take some time and share your thoughts: https://forms.gle/R6faU74qPRPAzchZ9

📣 If you've already given us your feedback, you can still help by spreading the news,
either by sharing the above link or telling people about this on Twitter:

https://twitter.com/sagikazarmark/status/1306904078967074816

Thank you! ❤️