For what it's worth, the Wikipedia page about this data structure calls it a
dynamic array, growable array, resizable array, dynamic table, mutable array, or array list
I prefer the term "array list" but that's probably just because of my background, and it's hard to give any objective argument for why one name should be preferred over others, beyond popularity or appeal to authority.
That said, it may be called simply a "list" in contexts where what matters is not the underlying data structure, but the abstract data type it implements. The contrast is between naming things by what they're made of (in this case, an "array list" is a list made from an array) vs. what they're used for. This isn't to imply that the word "list" actually means an array list, only that sometimes the fact that it's a list matters more than the fact that it's an array list.
Lower-level languages will tend to use names which describe the data structure, since programmers want control over which data structures are used; higher-level languages will tend to use names which describe the data type, since the programmers want a general-purpose way of solving problems without having to make choices about such implementation details. So it makes sense that e.g. Python has "lists" and "dictionaries" instead of "dynamic arrays" and "hashtables".
So I'd suggest calling it an "array list" or "dynamic array" if your language is making the programmer choose which data structures to use, or just "list" if your language is trying to make a sensible default choice so the programmer doesn't have to think about it. Put another way, if it's the only kind of list your language has first-class support for, then just call it a list.