fix(auth): default public_profile_allow_chat_with_me to true for new users

Aligns the User entity constructor and Doctrine column mapping so both
agree with the 2023 migration's DB-level default (1/true), closing the
code/DB contradiction flagged in ClickUp 86bbdxzt6. Previously the
constructor set false while the DB default was already 1, so new
accounts silently diverged from the intended on-by-default chat
setting once any code path relied on the DB default instead of the
explicit ORM insert.

Adds a unit test asserting a freshly constructed User defaults to
chat-allowed true.

Author: smarcet

app/libs/Auth/Models/User.php

@@ -109,7 +109,7 @@ class User extends BaseEntity
     /**
      * @var bool
      */
-    #[ORM\Column(name: 'public_profile_allow_chat_with_me', options: ['default' => 0], type: 'boolean')]
+    #[ORM\Column(name: 'public_profile_allow_chat_with_me', options: ['default' => 1], type: 'boolean')]
     private $public_profile_allow_chat_with_me;
 
     /**
@@ -464,7 +464,7 @@ public function __construct()
         $this->public_profile_show_social_media_info = false;
         $this->public_profile_show_bio = true;
         $this->public_profile_show_telephone_number = false;
-        $this->public_profile_allow_chat_with_me = false;
+        $this->public_profile_allow_chat_with_me = true;
 
         $this->password = "";
         $this->identifier = null;

tests/unit/UserMappingTest.php

@@ -29,6 +29,12 @@
  */
 class UserMappingTest extends BrowserKitTestCase
 {
+    public function testDefaultPublicProfileAllowChatWithMeIsTrue()
+    {
+        $user = new User();
+        $this->assertTrue($user->isPublicProfileAllowChatWithMe());
+    }
+
     public function testUserPersistence()
     {
         $email = 'test@nomail.com';