Fixed #23649 -- Made Oracle test-db creation drop test-user earlier when...

... needed

Checked database destruction for ORA-29857, which happens when objects of
some types are left over in an old test database (notably, such objects
are created by the GIS backend). When this happens, we can resolve the
issue by dropping the test-user (if we are allowed to).

An alternative approach, to just switch the order of creation (so that,
if the test user exists and can be dropped, it is always dropped before
the tablespace) was considered; but since the user creation depends on
the tablespace, this would necessitate separating the dropping of the user
from its creation -- a change I am reluctant to make.
I understand "manually" to mean "anything not done by Django".
Here, the intention was closer to "one by one". I'll use "find and remove each of these objects".