@Luis Daniel Mesa Velasquez Welcome to Microsoft Q&A thanks for posting your question.
SQL Server has / uses granular permission model. First, db_ddladmin only grants permissions to create or modify objects. This doesn't mean that you can read or modify data in those objects. So, a database user that is member of db_ddladmin can create a table but cannot insert or select from it. This is expected & by design.
Database-Level Roles - SQL Server | Microsoft Learn -- See the table & image in this topic.
- How do I get the SELECT, INSERT, UPDATE, DELETE grants for those 2 tables?
If you want to get these permissions in the context of a session, then use sys.fn_my_permissions with the appropriate securable name and securable class.
sys.fn_my_permissions (Transact-SQL) - SQL Server | Microsoft Learn
You can also get the permissions for any user on database objects using sys.database_permisisons.
sys.database_permissions (Transact-SQL) - SQL Server | Microsoft Learn -- Example B or C
Other than this, I have no idea what Liquibase does or doesn't do underneath the covers. I would recommend reaching out to the Liquibase documentation.
I hope this information helps.
Regards
Geetha