Weird that the config for a wrover kit works for ESP32-WROOM-32UE. Anways since you have selected board = esp32dev, the used openocd config file will be
Which may not be what you want. You can set board = esp-wrover-kit since that will give you
(or board_debug.openocd_board = esp32-wrover.cfg may work too).
To get openocd to use the 3.3V flash voltage you will have to edit the cfg file in C:\Users\<user>\.platformio\packages\tool-openocd-esp32\share\openocd\scripts\board\esp32-wrover.cfg yourself at the lines
# Tell OpenOCD which SPI flash voltage is used by the board (3.3 or 1.8)
# The TDI pin of ESP32 is also a bootstrap pin that selects the voltage the SPI flash
# chip runs at. When a hard reset happens (e.g. because someone switches the board off
# and on) the ESP32 will use the current TDI value as the bootstrap value because the
# JTAG adapter overrides the pull-up or pull-down resistor that is supposed to do the
# bootstrapping. These lines basically set the idle value of the TDI line to a
# specified value, therefore reducing the chance of a bad bootup due to a bad flash
# voltage greatly.
# This option defaults to 3.3, if not set. To override the default, uncomment
# the following line:
set ESP32_FLASH_VOLTAGE 1.8
which should be changed to 3.3.
If that still doesn’t work, it may really need the newest openocd version. In such a case you can try and replace the files locally in your C:\Users\<user>\.platformio\packages\tool-openocd-esp32 folder with updated binaries and scripts and see if that works out (while changing the to-be-used config file via openocd_board)