feat: remove compilation command

After thinking for some time, I've decided to get rid of compilation command. This would be useful to compile container and plugin data at build-time, but for the container the task is not trivial.

Compilation would require WordPress runtime, so the only viable solution would be to boot whole WordPress with database. Removing the use of WordPress functions wouldn't be possible or at least required some common WP functions to be rewritten in our codebase.

For current approach, I bias towards compilation in customer's environment at first runtime, with graceful handling of any IO operation issues.

Signed-off-by: Bart Jaskulski bjaskulski@protonmail.com

CHANGELOG.md

 # wp-init changelog
 
+## [0.10.4] - 2024-11-27
+### Fixed
+- When container cannot be compiled to disk, it will be used without cache.
+### Changed
+- Serious changes in `StoppableBinder` logic. It can only stop hookable classes from now, leaving the execution of callable shortcut bindings.
+- Improvements in dev environment detection – container is not compiled, when WordPress environment type is different from `production`.
+- Reverted: Move i18n filter to `init` hook for WordPress 6.7 compatibility.
+
 ## [0.10.3] - 2024-11-13
 ### Changed
 - Move i18n filter to `init` hook for WordPress 6.7 compatibility.