[Build] Replace message() in caffe2/CMakeLists.txt with message in cmake/Summary.cmake

[dhruvbird]

Stack from ghstack (oldest at bottom):

• [Metal] Update list of Metal supported operators in Model Tracer #84849
• [Mobile Tracer] Allow tracing multiple input models at once #84833
• -> [Build] Replace message() in caffe2/CMakeLists.txt with message in cmake/Summary.cmake #84814

Summary: In PR 84755, @cccclai noticed and mentioned the presence of message(STATUS...) logging in caffe2/CMakeLists.txt and suggested moving it to the file cmake/Summary.cmake. This PR addresses that comment/suggestion.

Test Plan: Ran the build as USE_NUMPY=0 USE_DISTRIBUTED=0 USE_CUDA=0 TRACING_BASED=1 python setup.py develop

and saw the follwing being printed:

--   BUILD_MOBILE_AUTOGRAD : OFF
--   BUILD_LITE_INTERPRETER: OFF
--   INTERN_BUILD_MOBILE   :
--   TRACING_BASED         : 1

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/84814

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit aba0db7:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[cccclai]

Looks great. Thanks!

[dhruvbird]

@pytorchbot merge

[pytorchmergebot]

@pytorchbot successfully started a merge job. Check the current status here.
The merge job was triggered without a flag. This means that your change will be merged once all checks on your PR have passed (ETA: 0-4 Hours). If this is not the intended behavior, feel free to use some of the other merge options in the wiki.
Please reach out to the PyTorch DevX Team with feedback or questions!

[github-actions]

Hey @dhruvbird.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.

[anjali411]

I am not sure if "topic: build" was added for release notes. If it was, then it should also be added to this list:

pytorch/.github/scripts/process_commit.py

Lines 23 to 32 in ccb1ff2

	"topic: bc_breaking",
	"topic: deprecation",
	"topic: new feature",
	"topic: improvements",
	"topic: bug fixes",
	"topic: performance",
	"topic: documentation",
	"topic: developer feature",
	"topic: not user facing",
	}

(cc. @malfet ).

Also, the bot ping for labeling given that the PR already had "release notes: " label before merge seems like a bug (cc. @atalman).