dealerdirect/phpcodesniffer-composer-installer contains a Composer plugin which is blocked by your allow-plugins config

[bukowa]

+ composer install
No composer.lock file present. Updating dependencies to latest instead of installing from lock file. See https://getcomposer.org/install for more information.
Loading composer repositories with package information
Info from https://repo.packagist.org/: #StandWithUkraine
Updating dependencies
Lock file operations: 4 installs, 0 updates, 0 removals
  - Locking dealerdirect/phpcodesniffer-composer-installer (v0.7.2)
  - Locking phpcompatibility/php-compatibility (9.3.5)
  - Locking squizlabs/php_codesniffer (3.7.1)
  - Locking wp-coding-standards/wpcs (2.3.0)
Writing lock file
Installing dependencies from lock file (including require-dev)
Package operations: 4 installs, 0 updates, 0 removals
  - Downloading squizlabs/php_codesniffer (3.7.1)
  - Downloading dealerdirect/phpcodesniffer-composer-installer (v0.7.2)
  - Downloading phpcompatibility/php-compatibility (9.3.5)
  - Downloading wp-coding-standards/wpcs (2.3.0)
 0/4 [>---------------------------]   0%
 3/4 [=====================>------]  75%
 4/4 [============================] 100%
  - Installing squizlabs/php_codesniffer (3.7.1): Extracting archive
In PluginManager.php line 769:

  dealerdirect/phpcodesniffer-composer-installer contains a Composer plugin w  
  hich is blocked by your allow-plugins config. You may add it to the list if  
   you consider it safe.                                                       
  You can run "composer config --no-plugins allow-plugins.dealerdirect/phpcod  
  esniffer-composer-installer [true|false]" to enable it (true) or disable it  
   explicitly and suppress this exception (false)                              
  See https://getcomposer.org/allow-plugins                                    

install [--prefer-source] [--prefer-dist] [--prefer-install PREFER-INSTALL] [--dry-run] [--dev] [--no-suggest] [--no-dev] [--no-autoloader] [--no-progress] [--no-install] [-v|vv|vvv|--verbose] [-o|--optimize-autoloader] [-a|--classmap-authoritative] [--apcu-autoloader] [--apcu-autoloader-prefix APCU-AUTOLOADER-PREFIX] [--ignore-platform-req IGNORE-PLATFORM-REQ] [--ignore-platform-reqs] [--] [<packages>...]

[etstaging]

QA Checklist

Reporter

• [ ] Helpful title used  
  • Helpful title format: Scope(s) :: One Sentence To Describe The Issue
  • Example: VB :: Floating Toolbar :: Jumps To Top Of Page
• [ ] Detailed description
  • Description should usually be 150+ characters.
• [ ] Steps to reproduce included
• [ ] Support Ticket URL included
• [ ] Image and/or gif

Developer

• [ ] Estimated points on issue
• [ ] Steps to reproduce proven solved
• [ ] PR description has layman's description of problem and solution and "Areas Affected" listed/explained?
• [ ] Proper RTL appearance

Peer Review

• [ ] PR branch includes latest commits from master branch (at the time of checking)?
• [ ] Steps to reproduce proven solved
• [ ] Affected areas are tested and ok
• [ ] Proper code documentation and conventions
• [ ] Proper RTL appearance
• [ ] i18n used if applicable
• [ ] Test(s) included and coverage acceptable
• [ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
• [ ] Database saved/updated? Data sanitized and validated?
• [ ] Variable output properly escaped and validated?

Quality Assurance

• [ ] All tests passed on CircleCI.
• [ ] Steps to reproduce passed, the fix works.
• [ ] No errors in console or output
• [ ] Affected areas are tested and ok
• [ ] The fix does not change a customer's website in any surprising or unintended way
  • [ ] If Divi's design is adjusted, settings are migrated gracefully and invisibly

Design Review

• [ ] UI is to spec
• [ ] UX is to spec
• [ ] Design is to spec
• [ ] No surprising visual changes to a customer's website will be experienced after updating
  • [ ] Any/all visual changes are migrated gracefully

Dev Review

• [ ] Test(s) included and coverage acceptable
• [ ] Ajax/Form used? Nonce used? Perms checked? All user input sanitized and validated? Intentional unsanitized/unescaped functions used?
• [ ] Database saved/updated? Data sanitized and validated?
• [ ] Variable output properly escaped and validated?
• [ ] i18n used if applicable
• [ ] Implementation acceptable, DRY, Scaleable, future safe
• [ ] Best practices used, cleverness and grokage, ES6 use, etc.

[bukowa]

To work need composer <= 2.1