## Environment
**Liquibase Version**: 4.3.1

**Liquibase Integration & Version**: n/a

**Liquibase Extension(s) & Version**: n/a 

**Database Vendor & Version**: Oracle and MSSQL

**Operating System Type & Version**: n/a

## Description
If you have an `addForeignKeyConstraint` change with attribute `deleteCascade="true"` it is simply ignored.
This code: https://github.com/liquibase/liquibase/blob/43ed0e54adedc5f12c7933b998550e777d9b683d/liquibase-core/src/main/java/liquibase/change/core/AddForeignKeyConstraintChange.java#L195-L199 suggests that it should be automatically translated to `onDelete="CASCADE"` which would make sense, but it is not.
It currently is simply ignored.


description = "Name of column(s) to place the foreign key constraint on. Comma-separate if multiple",
        exampleValue = "person_id",
        mustEqualExisting = "column"
    )
    public String getBaseColumnNames() {
        return baseColumnNames;
    }
    public void setBaseColumnNames(String baseColumnNames) {
        this.baseColumnNames = baseColumnNames;
    }
    @DatabaseChangeProperty(since = "3.0", mustEqualExisting = "column")
    public String getReferencedTableCatalogName() {
        return referencedTableCatalogName;
    }
    public void setReferencedTableCatalogName(String referencedTableCatalogName) {
        this.referencedTableCatalogName = referencedTableCatalogName;
    }
    public String getReferencedTableSchemaName() {
        return referencedTableSchemaName;
    }
    public void setReferencedTableSchemaName(String referencedTableSchemaName) {
        this.referencedTableSchemaName = referencedTableSchemaName;
    }
    @DatabaseChangeProperty(
        description = "Name of the table the foreign key points to",
        exampleValue = "person")
    public String getReferencedTableName() {
        return referencedTableName;
    }
    public void setReferencedTableName(String referencedTableName) {