Suggest catching the boost conversion_error exception also in bl_locale_set so that older systems won't crash if this code breaks them.

I have not been able to redo the crash ever since T88877#1187007, despite hardcoding en_IN or even ko-Kore_KR in the code. Would have to rely on @KIEUN MUN (kieuns) for testing.

Just FYI if you want to make this OS version dependent [1], that can be done.
[1] https://developer.apple.com/documentation/foundation/nsprocessinfo/1414876-isoperatingsystematleastversion?language=objc

Found a bug report similar to this. https://bugs.llvm.org/show_bug.cgi?id=37487 Don't know if any of the dependencies are responsible in our case or if it's a different issue.
Still present in clang version 13.0.0 (https://github.com/llvm/llvm-project.git 3b47bd32f9df4a57db98db5f35e680c7bd9fde3e), tested that gist.

However, the conversion_error is being caught properly now. 2.93, compiler version above. But since it's still happening with all those Big Sur users (or with blender compiled on a specific system), let's keep that extra catcher.

diff --git a/intern/locale/boost_locale_wrapper.cpp b/intern/locale/boost_locale_wrapper.cpp
index 73433fe7c5e..a5ed7caf53d 100644
--- a/intern/locale/boost_locale_wrapper.cpp
+++ b/intern/locale/boost_locale_wrapper.cpp
@@ -87,6 +87,7 @@ void bl_locale_set(const char *locale)
   // gen.set_default_messages_domain(default_domain);
 
   try {
+    throw boost::locale::conv::conversion_error();
     if (locale && locale[0]) {
       _locale = gen(locale);
     }
@@ -118,6 +119,7 @@ void bl_locale_set(const char *locale)
 #undef LOCALE_INFO
   }
   catch (std::exception const &e) {
+    std::cout << "Type:    " << typeid(e).name() << "\n";
     std::cout << "bl_locale_set(" << locale << "): " << e.what() << " \n";
   }
 }

Type: N5boost6locale4conv16conversion_errorE

Thanks for the review and improvements, will commit to 3.0 now.