chore: Update resource bundles (resolves #170, resolves #349)

fcli-core/fcli-fod/src/main/resources/com/fortify/cli/fod/i18n/FoDMessages.properties

@@ -22,7 +22,8 @@ fcli.fod.usage.description.1 = %nBefore being able to interact with FoD, a sessi
 
 # Mixins
 fcli.fod.app.app-name = Application name.
-fcli.fod.app.app-name-or-id = Application id or name.
+fcli.fod.app.app-name-or-id = Application id or name. Note that numeric values are always interpreted \
+  as id's. If you have numeric application names, you will need to specify the application id.
 fcli.fod.app.app-type = Application type. Valid values: ${COMPLETION-CANDIDATES}
 fcli.fod.app.release.microservice-and-release-name = Initial release to be created on the application, in the format <microservice>:<release> for a microservices application, or just <release> for non-microservices applications. 
 fcli.fod.scan.scan-id = Scan id(s).
@@ -40,12 +41,16 @@ fcli.fod.microservice.resolver.name = Microservice name in the format <applicati
 fcli.fod.release.resolver.name-or-id = Release id or <application>[:<microservice>]:<release> name.
 fcli.fod.release.resolver.name = Release name in the format <application>[:<microservice>]:<release>.
 fcli.fod.import.sbom-format = The SBOM format to import. If empty Cyclone DX format is assumed.
-fcli.fod.user.user-name-or-id = User id or username.
-fcli.fod.group.group-name-or-id = Group id or name.
+fcli.fod.user.user-name-or-id = User id or username. Note that numeric values are always interpreted \
+  as id's. If you have numeric user names, you will need to specify the user id.
+fcli.fod.group.group-name-or-id = Group id or name. Note that numeric values are always interpreted \
+  as id's. If you have numeric group names, you will need to specify the group id.
 fcli.fod.filters-param = Server-side queries are automatically generated from the -q / --query option if possible; \
   generated queries can be viewed in the debug log. The --q-param option can be used to override the automatically generated query, \
   for example to further optimize the request. See the Fortify on Demand REST API documentation for information on supported formats.
-fcli.fod.app-name-or-id = Application id or name.
+fcli.fod.app-name-or-id = One or more comma-separated application id's or name's. Note that numeric values \
+  are always interpreted as id's. If you have numeric application names, you will need to specify the \
+  application id.
 
 # Shared options
 scan-id's[0] = One or more scan id's; supports '-' to reference a scan id previously stored using '--store -'

fcli-core/fcli-ssc/src/main/resources/com/fortify/cli/ssc/i18n/SSCMessages.properties

@@ -150,7 +150,8 @@ fcli.ssc.app.list.usage.header = List applications.
 fcli.ssc.app.update.usage.header = Update an application.
 fcli.ssc.app.update.name = New name for the application.
 fcli.ssc.app.update.description = New description for the application.
-fcli.ssc.app.resolver.nameOrId = Application name or id.
+fcli.ssc.app.resolver.nameOrId = Application name or id. Note that numeric values are always interpreted \
+  as id's. If you have numeric application names, you will need to specify the application id.
 
 # fcli ssc appversion
 fcli.ssc.appversion.usage.header = Manage SSC application versions.
@@ -168,10 +169,23 @@ fcli.ssc.appversion.download-state.usage.description = Download application vers
 fcli.ssc.appversion.get.usage.header = Get application version details.
 fcli.ssc.appversion.get.embed = Embed extra application version data. Allowed values: ${COMPLETION-CANDIDATES}.
 fcli.ssc.appversion.list.usage.header = List application versions.
+fcli.ssc.appversion.list.usage.description = By default, this command simply lists all application \
+  versions. However, the --embed, --query and --output options allow for implementing advanced use cases. \
+  Some examples: \
+  %n%n List application versions created by user 'admin': \
+  %n -q 'createdBy=="admin"' \
+  %n%n List application versions requiring refresh: \
+  %n -q 'refreshRequired' \
+  %n%n List application versions with artifacts requiring approval: \
+  %n -q 'currentState.attentionRequired' \
+  %n%n List application versions with business risk 'High': \
+  %n --embed attrValuesByGuid -q 'attrValuesByGuid["BusinessRisk"].contains("High")' \
+  %n%n Generate script for purging all application versions: \
+  %n -o 'expr=fcli ssc appversion purge-artifacts --older-than 30d {id}\\n'
 fcli.ssc.appversion.list.embed = Embed extra application version data. Allowed values: ${COMPLETION-CANDIDATES}. \
-  Apart from potentially including the extra data in the output, this allows for advanced queries like the \
-  following to query application versions by application version attribute values: \
-  'attrValuesByName["Interfaces"].contains("Interactive Console")'. 
+  Using the --output option, this extra data can be included in the output. Using the --query option, \
+  this extra data can be queried upon. To get an understanding of the structure and contents of the \
+  embedded data, use the --output json or --output yaml options. 
 fcli.ssc.appversion.purge-artifacts.usage.header = Purge application version artifacts.
 fcli.ssc.appversion.purge-artifacts.usage.description = Purge all application version artifacts older than the specified date. See 'fcli ssc artifact purge' for purging individual artifacts. 
 fcli.ssc.appversion.purge-artifacts.older-than = Purge artifacts older than the specified value, \
@@ -231,7 +245,7 @@ fcli.ssc.artifact.import-debricked.engine-type = SSC engine type. Default value:
 fcli.ssc.artifact.import-debricked.save-sbom-as = Save a copy of the SBOM file downloaded from \
   Debricked to the given file.
 fcli.ssc.artifact.import-debricked.repository = Debricked repository name or id.
-fcli.ssc.artifact.import-debricked.branch = Branch in the given repository for which to retrieve \the SBOM.
+fcli.ssc.artifact.import-debricked.branch = Branch in the given repository for which to retrieve the SBOM.
 fcli.ssc.artifact.import-debricked.insecure = Disable SSC checks when connecting to Debricked.   
 fcli.ssc.artifact.upload.usage.header = Upload an artifact.
 fcli.ssc.artifact.upload.engine-type = Engine type specifying which SSC parser plugin should be \