Any Reason why there can only be one job table inside schema cron on postgres or configured?

Hello I'm actually quite loving the pg_cron extensions, it allows for small users a really simple mechanism to create High Available Cron Jobs.

However managing these are quite a bit painful.
Is there any reason why the metadata tables is expected to be a single one?

Isn't there a way to actually do `CREATE EXTENSION pg_cron;` and it would be possible to select all the jobs of the current user, schedule/unschedule them?

Currently we use jdbc and if we don't want to open up a second connection to the postgres database, we would need to reconfigure the cron extension everywhere (well sadly we need to configure `shared_preload_libraries` anyway...).
this looks a little bit of an overhead, especially since we want to still use our flyway migrations to insert new cron jobs.
Is there any "best practice"/no-go on what's the best way to integrate pg_cron inside an application?

(At the moment we actually have a single cron.schedule that calls
`SELECT pg_notify('our_channel', '{"type": "nightly"}')`. Which we registerted with `cron.schedule` and then updated the cron.job database column.