The log2ram package installs its logrotate configuration file inside a
subdirectory under /etc/logrotate.d/, which causes logrotate to ignore it.

Actual  logrotate file installation path:
  /etc/logrotate.d/log2ram/log2ram.logrotate

Reproduction steps and logs:

1. Install log2ram:

Get:1 http://deb.debian.org/debian trixie/main arm64 log2ram arm64
1.7.2+ds-1 [7,724 B]
Fetched 7,724 B in 0s (47.6 kB/s)
Selecting previously unselected package log2ram.
(Reading database ... 68830 files and directories currently installed.)
Preparing to unpack .../log2ram_1.7.2+ds-1_arm64.deb ...
Unpacking log2ram (1.7.2+ds-1) ...
Setting up log2ram (1.7.2+ds-1) ...
Created symlink '/etc/systemd/system/sysinit.target.wants/log2ram.service'
→ '/usr/lib/systemd/system/log2ram.service'.
Created symlink
'/etc/systemd/system/timers.target.wants/log2ram-daily.timer' →
'/usr/lib/systemd/system/log2ram-daily.timer'.
#####         Reboot to activate log2ram         #####
##### edit /etc/log2ram.conf to configure options ####
Processing triggers for man-db (2.13.1-1) ...

2. Inspect the installed logrotate directory:

$ ll /etc/logrotate.d/log2ram/
total 12K
drwxr-xr-x 2 root root 4.0K Dec 15 09:05 ./
drwxr-xr-x 3 root root 4.0K Dec 15 09:05 ../
-rw-r--r-- 1 root root   97 Jun 12  2024 log2ram.logrotate

3. Run logrotate in debug mode:

$ sudo logrotate -d /etc/logrotate.conf
warning: logrotate in debug mode does nothing except printing debug
messages!  Consider using verbose mode (-v) instead if this is not what you
want.

reading config file /etc/logrotate.conf
including /etc/logrotate.d
reading config file alternatives
reading config file apt
reading config file backup
reading config file btmp
reading config file cloud-init
reading config file dpkg
Ignoring log2ram because it's not a regular file.
...

Expected behavior:
  The package should install a single file directly under
/etc/logrotate.d/, e.g.:
    /etc/logrotate.d/log2ram

System:
  Debian trixie (arm64, Raspberry Pi 5)

Thanks.