chore: document maven-compiler-plugin new behavior

Relate to #1560

[skip ci]

Author: php-coder

docs/decisions-log.md

@@ -2,6 +2,7 @@
 
 | Date/Type | Description |
 | --------- | ----------- |
+| 28.01.2024 Workaround | Draft: maven-compiler-plugin creates useless `package-info.class` files that I had to exclude Commit: [e1d4c49d](https://github.com/php-coder/mystamps/commit/e1d4c49d5bece72bcaff31afcd7f784044df0ec2) Issue: [php-coder/mystamps#1560](https://github.com/php-coder/mystamps/issues/1560)
 | 24.12.2023 Workaround | Draft: Liquibase broke `afterColumn` attribute and suggest to use `<removeChangeSetProperty>` but it can't be applied globally and I had to specify it everywhere. Issue: [php-coder/mystamps#1565](https://github.com/php-coder/mystamps/issues/1565) PR: [php-coder/mystamps#1651](https://github.com/php-coder/mystamps/pull/1651) Commit: [5f89210a4](https://github.com/php-coder/mystamps/commit/5f89210ae02ec830c1be6f594870d965563d6804) Bug: [liquibase/liquibase#5290](https://github.com/liquibase/liquibase/issues/5290) |
 | 20.07.2023 Decision | [php-coder/mystamps#1154](https://github.com/php-coder/mystamps/issues/1154): some time ago (29.11.2022) **Travis CI** [stopped to work](https://github.com/php-coder/mystamps/issues/1154#issuecomment-1330014938) because of the changes in their policy. On 04.12.2022 [I contacted with support and got 25k credits](https://github.com/php-coder/mystamps/issues/1154#issuecomment-1336413246) and CI has started to work again. This was a signal to try **GitHub Actions** as it's more stable, feature-rich and native for GitHub. Today (20.07.2023) a migration has finished and the project now is fully moved to GitHub Actions |
 | 22.06.2023 Workaround | [php-coder/mystamps#1610](https://github.com/php-coder/mystamps/issues/1610): in the `connect-todos-to-issues.sh` script, we want to search issues that a) contains puzzle id in their body b) has a title like we have in a puzzle. The former condition covers the case when a puzzle id already has a related issue. The latter is for the case when puzzle id got changed but the title remains the same (for example, because of changing an intepretation of the comments) -- this is how we try to find an issue that was connected to an old puzzle. The limitation that I faced is that **`gh`** utility can't use *logical OR* in the search conditions. I added a workaround where we first search in body, after that by title, and at the end we merge the results together. Commit: [c02dc39a](https://github.com/php-coder/mystamps/commit/c02dc39a7357d30e8c8f74c346e5fc4b81122140) |