Survey123 captures dates in "Epoch" or "Unix" time, which is to say seconds or milliseconds since Jan 1 1970.
This causes all sorts of fun for conversions in other systems, in fact sometimes I'm not sure if the Survey123 feature classes knows quite how to handle it. Although that's partly timezone issues I'm sure, but I digress.
In my power automate fields I create an expression like:
addSeconds('1970-1-1', Div(triggerOutputs()?['body/feature/attributes/survey_date'], 1000), 'yyyy-MM-dd')
This takes any given date (in epoch time) coming from survey123 and returns a string like '2023-06-08', format as you please!