DNS over HTTPS and DNS over TLS offer equivalent security in terms of encryption and integrity. That's because HTTPS is essentially HTTP over TLS. There are certainly various versions of TLS and various algorithms, and some are better than others, but assuming a secure set of algorithms and parameters, they provide equivalent security. Both of them are designed to provide privacy, integrity, and authenticity to and from the recursive DNS resolver you're using for your network.
DNS over TLS does provide some advantages in that neither side needs to implement HTTP. HTTP is a complicated protocol which requires careful parsing, and an HTTP implementation may have additional security vulnerabilities or performance penalties that a plain DNS over TLS implementation would not. The main advantage of DNS over HTTPS is that it's harder to filter out than DNS over TLS because it goes over the HTTPS port and an attacker cannot determine easily what the contents are. (In this case, the attacker could well be your network administrator or local government.)
Now, none of these tell you whether the data you received is what the zone owner put in the zone. DNSSEC is a system of digitally signing DNS records such that they are unable to be modified except by the owner of the zone. Its use is controversial, but it does prevent attacks from things like captive portals substituting fraudulent DNS records.