Probably due to code drift, `HookRegisteringBeanDefinitionRegistryPostProcessor.setupHooks` was used as an object method, which led to a confusing no-op chain in tests. This ensures it is used consistently as a static method, and also corrects a bean accidentally marked static for testing.