Письменов Дмитрий Иванович / yourroomads

Bump symfony/http-foundation from 4.4.2 to 4.4.7

Bumps [symfony/http-foundation](https://github.com/symfony/http-foundation) from 4.4.2 to 4.4.7.
- [Release notes](https://github.com/symfony/http-foundation/releases)
- [Changelog](https://github.com/symfony/http-foundation/blob/master/CHANGELOG.md)
- [Commits](https://github.com/symfony/http-foundation/compare/v4.4.2...v4.4.7)

Signed-off-by: dependabot[bot] <support@github.com>

Hash password only once

When a user resets their password, the password would be double hashed and the user locked out of their account.

Ensure we only hash the password if it needs to be hashed. If it has already been hashed, just return the password as-is.

Add extra setup details to README

Upgrade to tailwind v1.0 (continued work)

Thanks to @freekmurze for confirming this is safe, and won't expose any environment variables

Use `npm ci` to avoid package-lock update

Running `npm ci` instead of `npm install` avoids `package-lock` file update and installation of patch versions different from upstream.

This can be useful to avoid git pollution and to have exactly the same version of npm dependencies when debugging or writing an example to reproduce an issue.

`npm ci` was added to NPM to be used in Continuous Integration setups (hence the `ci`) keeping exactly the same versions of packages listed in package-lock file.