Support for Frogbot PR and Repository scanning.

Is your feature request related to a problem? Please describe.
The current process for integrating Frogbot into Azure DevOps pipelines is not clearly documented and requires manual handling of credentials—even though a service connection or service account is already available through the Azure DevOps environment. This creates unnecessary complexity and hinders adoption.

Describe the solution you'd like to see
I would like to see two new pipeline steps added to this repository that provide native support for Frogbot integration using the JFrog Azure DevOps extension. These steps should handle authentication through the existing service connection and abstract away the manual configuration currently required.

Ideally, the solution should also support a single unified step that can automatically detect whether it is being triggered by a pull request or a standard branch build using Build.Reason. This would allow conditional execution of PR scanning vs. repository scanning within the same task.

Describe alternatives you've considered
Wrapping the existing Frogbot templates from the official documentation into reusable YAML templates for Azure DevOps. However, this still requires custom handling of credentials and context detection.

Manually scripting the distinction between PR and branch scanning using environment variables, which adds complexity and maintenance overhead.

Start by reviewing the existing Frogbot templates from the official documentation and the JFrog Azure DevOps extension entry points mentioned in the request. Define how separate PR and repository scanning steps, or one step using Build.Reason, consume the existing service connection; done means both scan modes authenticate without manual credential handling.