Fix the way action set name was being configured

[viveksinghggits]

Change Overview

Fixes: #2285

kanctl was able to configure the actionset name using the flag called action-set.
But it had two problems

1. The better flag to give actionset name would be --name instead of --action-set. Because there is another flag called action, so it gets confusing between --action-set and --action. This PR renames the flag to provide the actionset name to --name.
2. Even though user would expect that if they have provided --name the actionset would be named exactly that. But the problem was we were using generateName in code that resulted in a string being added in the name. This PR makes sure that if --name is provided, the actionset would have exactly this name.

Pull request type

Please check the type of change your PR introduces:

• 🚧 Work in Progress
• 🌈 Refactoring (no functional changes, no api changes)
• 🐹 Trivial/Minor
• 🐛 Bugfix
• 🌻 Feature
• 🗺️ Documentation
• 🤖 Test

Issues

• fixes Dynamic Naming of Actionsets using kanctl #2285

Test Plan

go test 
OK: 3 passed
PASS
ok  	github.com/kanisterio/kanister/pkg/kanctl	0.031s

• 💪 Manual
• ⚡ Unit test
• 💚 E2E

kanctl create actionset --action backup --namespace kanister --blueprint mysql-blueprint --statefulset mysql/mysql-release --profile mysql/s3-profile-qgbmj --dry-run
apiVersion: cr.kanister.io/v1alpha1
kind: ActionSet
metadata:
  creationTimestamp: null
  name: backup-wvb4r

kanctl create actionset --action backup --namespace kanister --blueprint mysql-blueprint --statefulset mysql/mysql-release --profile mysql/s3-profile-qgbmj --name=newname --dry-run
apiVersion: cr.kanister.io/v1alpha1
kind: ActionSet
metadata:
  creationTimestamp: null
  name: newname
spec:

kanctl create actionset --action restore --from=backup-6cztn --dry-run --profile mysql/s3-profile-qgbmj -n kanister
apiVersion: cr.kanister.io/v1alpha1
kind: ActionSet
metadata:
  creationTimestamp: null
  name: restore-backup-6cztn-cmlrl
spec:

[PrasadG193]

LGTM