Deploying Oracle ADW Changes from development environment to production
Key Infrastructure Pieces

Code Repository/Version Control System
Separate (and licensed) Dev/Test/Prod environments

You seem to be missing the Test environment.
Test Environment
I highly recommend using a Test environment.  One advantage is: You can use the actual Schema's name irregardless of environment.
One way to use the Test environment:

Clone Prod to Test

usually a clone of a pluggable database


apply Change scripts
perform Unit Tests

Automatic Test Scripts
There is a PL/SQL based Unit Testing package on GitHub ( utPLSQL ).
But, if you want an Oracle product, SQL Developer has Unit Testing capabilities.
You'll most likely need to create the scripts that interface with your automation software.
Automatic Schema Changes
Your second link mentioned LiquiBase.  This is now integrated into SQL Developer. Demo for Dev Schema to Prod Schema is available here.
You will use the new command line interface (SQLcl) for automation, not SQL Plus.
Another alternative (for new tables) is the SQL Developer Cart feature. It can also work well for creating the INSERT scripts for the small Dimension Tables.
Code Review
One thing you may want to incorporate into your process is a way to automate parts of the Code Review process.  I believe the key words to search in Google/Bing are &quot;code sniffer&quot;.
SQL Developer has a custom highlighting feature that I use to detect &quot;bad code&quot;.
Example

TO_DATE() without a format.
commit inside of a loop.
when others then null ( other forum ).

The review process is manual for me.  But, the custom highlighting helps the human code reviewer.
TL;DR
You need to look at SQL Developer's set of features.