Update Kanctl to Create profile with secret CredentialType

[SupriyaKasten]

Change Overview

Update Kanctl to Create profile with secret CredentialType

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

• #XXX

Test Plan

 kanctl create profile s3compliant --bucket ssk-test --access-key ${AWS_ACCESS_KEY_ID} --secret-key ${AWS_SECRET_ACCESS_KEY}               --region us-west-2   --namespace supriya -R "ValidRolel"  --dry-run 

apiVersion: v1
kind: Secret
metadata:
  creationTimestamp: null
  name: s3-secret-6q4c58
  namespace: supriya
stringData:
  access_key_id: ValidID
  role: validRole
  secret_access_key: ValidKey
---
apiVersion: cr.kanister.io/v1alpha1
credential:
  keyPair: null
  secret:
    apiVersion: ""
    group: ""
    kind: ""
    name: s3-secret-6q4c58
    namespace: supriya
    resource: ""
  type: secret
kind: Profile
location:
  bucket: ssk-test
  endpoint: ""
  prefix: ""
  region: us-west-2
  type: s3Compliant
metadata:
  creationTimestamp: null
  generateName: s3-profile-
  namespace: supriya
skipSSLVerify: false

• 💪 Manual
• ⚡ Unit test
• 💚 E2E

[tdmanv]

isn't this specific to S3?

[SupriyaKasten]

Currently we validate the profile to check for SecretType when credentialType = "Secret" and role != ""