Hello, the easiest is to modify the starter pack LocalAccounts template. Rename all matches for email with phone (Do it case sensitive) and ensure the following elements into your SelfAsserted-LocalAccountSignin-Phone technical profile:
<Metadata>
<Item Key="setting.operatingMode">Username</Item>
</Metadata>
And in your AAD-UserWriteUsingLogonPhone:
<PersistedClaims>
<PersistedClaim ClaimTypeReferenceId="phoneNumber" PartnerClaimType="signInNames.phoneNumber" />
</PersistedClaims>
Alternatively, you might add validation technical profile that targets a REST API (developed by you) that will call MS Graph to add the phone as strong verification method (MFA).
My bad, I've corrected my statement. No it would not send the verification code. It can be done, let me take a look and let you know of possible changes.
I took a look to the refered Phone Sign UP User Flow (custom policy actually). The changes required will be more to basically match my first suggestion. Please try it first and if there's something lacking or in excess let me know.