Relocate hazelcast-remote-controller [DI-639]

[JackPGreen]

In hazelcast/hazelcast-remote-controller#75, hazelcast-remote-controller is deployed to a different repository to address build issues. Update the paths to suit.

Also:

• updated Maven central URL as per https://github.com/hazelcast/hazelcast-mono/pull/4897
• updated Maven central URL to use HTTPS, as HTTP is no longer supported.

Fixes: DI-639

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 93.47%. Comparing base (ef8f568) to head (77fe5d4).
⚠️ Report is 5 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1556      +/-   ##
==========================================
+ Coverage   93.45%   93.47%   +0.01%     
==========================================
  Files         466      466              
  Lines       16628    16628              
  Branches     1350     1350              
==========================================
+ Hits        15540    15543       +3     
+ Misses        797      794       -3     
  Partials      291      291              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nishaatr]

LGTM
nit - title is little confusing. Something like Fetch hazelcast-remote-controller artifacts (EE SNAPSHOT) from JFrog. I was expecting some relocation but its simply repoint