Use authentication enabled docker for integration test

[chilagrow]

Description

For task test-integration-mongodb, the image mongodb_secured is used which has authentication and authorization enable. It already has an user created in docker.
Calling setup.SetupWithOpts(t, &setup.SetupOpts{SetupUser: true}) creates an user with root authorization permission at the beginning of the test, use that authenticated user for the test and drops the user at the end. Since all test share the users in admin.system.users database, the unique username is used for each test.

For task test-integration-postgresql and task test-integration-sqlite the listener is created within setup, and each test creates its own independent postgresql database or sqlite directory, so no other test accesses it.
Calling setup.SetupWithOpts(t, &setup.SetupOpts{SetupUser: true}) creates an user using local exception at the beginning of the test, and entire postgresql database is dropped at the end of the test.

• postgresql example postgres://username@127.0.0.1:5432/testcommandsauthenticationlogoutauthenticateduser
• sqlite example file:../tmp/sqlite-tests/testcommandsauthenticationlogoutauthenticateduser/

Closes #4100.

Readiness checklist

• I added/updated unit tests (and they pass).
• I added/updated integration/compatibility tests (and they pass).
• I added/updated comments and checked rendering.
• I made spot refactorings.
• I updated user documentation.
• I ran task all, and it passed.
• I ensured that PR title is good enough for the changelog.
• (for maintainers only) I set Reviewers (@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.
• I marked all done items in this checklist.

[codecov]

Codecov Report

Attention: Patch coverage is 92.98246% with 4 lines in your changes are missing coverage. Please review.

Project coverage is 73.81%. Comparing base (58ff7b0) to head (b063d16).

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #4160      +/-   ##
==========================================
- Coverage   73.85%   73.81%   -0.04%     
==========================================
  Files         339      339              
  Lines       22786    22827      +41     
==========================================
+ Hits        16828    16850      +22     
- Misses       4676     4691      +15     
- Partials     1282     1286       +4     

Files	Coverage Δ
internal/handler/common/find.go	100.00% <100.00%> (ø)
integration/setup/setup.go	83.62% <97.22%> (+2.24%)	⬆️
integration/setup/client.go	80.48% <85.00%> (+4.29%)	⬆️

... and 7 files with indirect coverage changes

Flag	Coverage Δ
filter-true	67.15% <92.98%> (-0.16%)	⬇️
integration	67.15% <92.98%> (-0.16%)	⬇️
mongodb-1	5.12% <87.71%> (+0.22%)	⬆️
postgresql-1	46.52% <61.40%> (-0.10%)	⬇️
postgresql-2	49.51% <61.40%> (+0.12%)	⬆️
postgresql-3	49.88% <61.40%> (+0.58%)	⬆️
sqlite-1	45.69% <61.40%> (-0.07%)	⬇️
sqlite-2	48.73% <61.40%> (+0.19%)	⬆️
sqlite-3	?
unit	32.55% <0.00%> (+<0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

[rumyantseva]

Cool! This will also help with sessions testing too :)

[AlekSi]

I will check the security workflow failure