## 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.


this.referencedTableName = referencedTableName;
    }
    @DatabaseChangeProperty(
        description = "Column(s) the foreign key points to. Comma-separate if multiple",
        exampleValue = "id")
    public String getReferencedColumnNames() {
        return referencedColumnNames;
    }
    public void setReferencedColumnNames(String referencedColumnNames) {
        this.referencedColumnNames = referencedColumnNames;
    }
    @DatabaseChangeProperty(description = "Name of the new foreign key constraint", exampleValue = "fk_address_person")
    public String getConstraintName() {
        return constraintName;
    }
    public void setConstraintName(String constraintName) {
        this.constraintName = constraintName;
    }
    @DatabaseChangeProperty(description = "Is the foreign key deferrable")
    public Boolean getDeferrable() {
        return deferrable;
    }
    public void setDeferrable(Boolean deferrable) {
        this.deferrable = deferrable;
    }
    @DatabaseChangeProperty(description = "Is the foreign key initially deferred")
    public Boolean getInitiallyDeferred() {
        return initiallyDeferred;
    }
    /**