[WebOTP] Update backend flag expiry date, owners, and desc

We are planning to start the devtrial for the new backend in the next
two milestones so updating the flag expiry to reflect this.


Bug: 1101050
Change-Id: Ife0ad995225169ec0e3705dfa66d1d5e3706880c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2546992
Reviewed-by: Yi Gu <[email protected]>
Commit-Queue: Yi Gu <[email protected]>
Auto-Submit: Majid Valipour <[email protected]>
Cr-Commit-Position: refs/heads/master@{#828871}
diff --git a/chrome/browser/flag_descriptions.cc b/chrome/browser/flag_descriptions.cc
index 55d500d4..6632525f 100644
--- a/chrome/browser/flag_descriptions.cc
+++ b/chrome/browser/flag_descriptions.cc
@@ -2422,8 +2422,7 @@
 const char kWebOtpBackendName[] = "Web OTP";
 const char kWebOtpBackendDescription[] =
     "Enables Web OTP API that uses the specified backend.";
-const char kWebOtpBackendSmsVerification[] =
-    "SMS Verification API (requires app-hash)";
+const char kWebOtpBackendSmsVerification[] = "Code Browser API";
 const char kWebOtpBackendUserConsent[] = "User Consent API";
 const char kWebOtpBackendAuto[] = "Automatically select the backend";