(fix/refactor): Remove unnecessary calls to Notification APIs (IDETECT-4992)

[shantyk]

Goal: Remove or replace expensive notification API usage in Detect (as per request from perflab) without changing existing behaviour.

Related blackbuck-common PR that must be merged and released first: blackducksoftware/blackduck-common#475. This will be a major version bump as the removal of the now unused "get latest user notification timestamp" API is a breaking change.

Summary of changes:

1. Safe removal of calls to notifications API in places where we do not need it:
► detector and signature (uses BOM status polling in all cases)
► binary (uses BOM status polling, except when server version is too old for multipart upload)
► impact analysis (currently no mechanism for checking the completion status. See HUB-25142)
► iac (never used notification based waiting, noop)

2. For remaining notification use cases, reduce API calls by simply using upload start time as the polling window start.

Previously, two API calls were made for each code location upload: one to fetch the current user and another to fetch the user’s notifications. The timestamp of the most recent notification becomes a given code location's NotificationTaskRange.startDate.
All ranges were eventually combined to derive the earliest polling start date.
This happened before Detect even checked whether waiting for results was required or whether BOM status polling was available instead.

New behavior:

Now we have codeLocationsUploadStartTime, recorded at code location upload initiation which eliminates per-upload API calls (and potential for race conditions from server delays, caching, or persistence lags, etc) and is a tighter start for the notification window than querying the most recent notification date (which will always be earlier or equal to upload start so we are certain to count only notifications from this Detect run).

If and when needed, notifications APIs are used for polling as they were before, only the starting timestamp has changed.
3. Removal of waitAtScanLevel boolean which simply represented if BD sever version exists and it is >=2023.1.1. 2023.1.x has reached end of support.
4. Docs: release note + updating wait property to indicate iac and impact analysis tools are not applicable.

Note on where we still use notification APIs:

In the case of a binary scan against a BD version < 2024.7.0, we use pre-SCASS binary scan with legacy upload mechanism (no multiparty upload possible). In this specific case, we mustWaitAtBomSummaryLevel for completion if detect.wait.for.results is set to TRUE. Though we will no longer make API calls to determine most recent notification, we will still eventually poll the notifications endpoint. In this case, we will see in the logs:

DEBUG [main] --- Using legacy binary scan upload method. This can be slow, consider upgrading to a newer version of Black Duck SCA to enable multipart uploading if possible.
INFO  [main] --- Preparing to upload binary scan file: /Users/shanty/blackduck/example-source/binaries/ifm.tar
DEBUG [main] --- Will use old notifications based waiting for the following code locations: [ifm.tar/shanty-testing/testing binary]
...
DEBUG [main] --- Will use old notifications based waiting for the following code locations: [ifm.tar/shanty-testing/testing binary]
DEBUG [main] --- Notifications after Tue Apr 14 04:47:10 MDT 2026 will be considered.
DEBUG [main] --- Expected notification count 1
DEBUG [main] --- Expected code locations:
DEBUG [main] ---   Code Location -> ifm.tar/shanty-testing/testing binary
DEBUG [main] --- 
DEBUG [main] --- At least one code location has been found, now looking for notifications.
DEBUG [main] --- There were 2 notifications found.
INFO  [main] --- All code locations have not been added to the BOM yet...
INFO  [main] --- Try #1 for task code location (elapsed: 00:00:00.000)...not done yet, waiting 60 seconds and trying again...
DEBUG [main] --- At least one code location has been found, now looking for notifications.
DEBUG [main] --- There were 3 notifications found.
INFO  [main] --- Found ifm.tar/shanty-testing/testing binary code location (1 of 1).

[shantyk]

Just moved to make try/catch block tighter around different exceptions expected, instead of one big umbrella try/catch.

[bd-samratmuk]

thanks for changing these names, massive w! 👍