feature: The instance generated by DubboReference supports calling applyBeanPostProcessorsAfterInitialization

[ph3636]

What is the purpose of the change

There are some requirements to proxy DubboReference。

for example
#7615

Brief changelog

Verifying this change

• Make sure there is a GitHub_issue field for the change (usually before you start working on it). Trivial changes like typos do not require a GitHub issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
• Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist #XXX. Each commit in the pull request should have a meaningful subject line and body.
• Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
• Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add sample in dubbo samples project.
• Run mvn clean install -DskipTests=false & mvn clean test-compile failsafe:integration-test to make sure unit-test and integration-test pass.
• If this contribution is large, please follow the Software Donation Guide.

[24kpure]

one feature with one commit maybe more cleaner

[ph3636]

one feature with one commit maybe more cleaner

Sorry, I don't understand what you mean. Is it because the direct use of applyBeanPostProcessorsAfterInitialization has a wide range of influence? How to design it reasonably, please guide me, because I think the normal initialization FactoryBean needs to go through applyBeanPostProcessorsAfterInitialization

[AlbumenJ]

@ph3636 Thanks for your contribution.
I will merge it later.
Would you please add some unit test cases for this PR?

[ph3636]

@AlbumenJ OK, it's already here.#7790