Fix: any_jest broken on Jihu side

What does this MR do and why?

• Rename any_jest to ee_else_ce_jest here since this is what it really does.
• Replace any_jest in the existing file.

Why

You can see in the changed file jest.config.config.js that when it comes to the Jihu edition, any_jest points to jh/specs/frontend/$1, when Jihu does not have any desired files, the test would simply fail. So I renamed the path for its real purpose, it might seem a little bit longer than before, but it is the right naming IMHO.

/cc @prajnamas

Describe in detail what your merge request does and why.

Screenshots or screen recordings

These are strongly recommended to assist reviewers and reduce the time to merge your change.

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.