Standardized the composer file

[kayw-geek]

• Standardize composer file
• Ignore commit of lock file
• Unlock the version of nikic/php-parser

[liby]

• Ignore commit of lock file
• Unlock the version of nikic/php-parser

Thank you for your contribution. However, the current practice of pinning the version of nikic/php-parser and committing the lock file in the repository is done intentionally for specific reasons.

Pinning the version helps us ensure that all developers and environments are using the exact same version of the dependency, which can help prevent bugs that might occur due to differences in dependency versions.

Including the lock file in the repository ensures that everyone installs the exact same dependencies, which is important for achieving reproducible builds and for ensuring that our application behaves the same way in all environments.

We appreciate your effort, but we would need compelling reasons to change these practices. Could you please explain the benefits of the changes you proposed?

[rainx]

@kayw-geek (Kai) Thanks for contributing. one more thing to clarify. we are using conventional commits on this project. so please read the doc ( https://www.conventionalcommits.org/en/v1.0.0/ ) to see how to write the commit message. if you have Node.JS installed, please run pnpm install to enable Husky. there would be a pre-commit lint to ensure the commit message is correct.

[kayw-geek]

@liby I don't know if we can accept the change range of the upstream package.
Can it be changed to "nikic/php-parser": "~4.17.1" or "nikic/php-parser": "~4.17" without limiting the patch or minor version?