ADT is creating packages instead of Driver Packages about driverautomationtool

[R4PH1]

This is how DAT operates per default as far as I remember with SCCM.
Just as a thought input. It is better to have the drivers as regular package instead of the need to import every individual driver into the database, creating the driver package out of them and linking them in your task sequences. Better on huge file and download then the slow multi file download. I highly recommend using the .wim compression too.
If you have other questions the community may support you.

[DoubleM-DCDSB]

So how can I install the drivers during a task sequence since the add a driver package only shows Driver Packages.

[R4PH1]

You need to implement point 2 and 4 from here: https://msendpointmgr.com/modern-driver-management/
Plus the type of imaging you are doing. I assume BareMetal. My task sequence step for run powershell script:
Script name: Invoke-CMApplyDriverPackage.ps1
Parameters: -BareMetal -Endpoint "server.domain.local" -TargetOSVersion "22H2"