Fix small TtlPIcker2 bug

[Monkeychip]

This fixes two specific situations:

1. a model using openApi with the following model attr.
2. a model NOT using openApi with the following model attr.

  @attr({
    label: 'someLabel',
    editType: 'ttl',
    hideToggle: true,
  })
  someParamName

The problem is that if a user does not set the defaultValue in situation 1 the openApi sends a value (if it has one defined). And in the case for PKI roles that was an integer. This may change after a discussion with the backend because that's not the value the API docs declare.

In situation 2 this fix makes is so if you don't pass any defaultValue then the TtlPicker2 doesn't show you passing a value. It shows a blank too.

*Note, the previous PKI engine has been sending the integer 30 for the param notBeforeDuration even though the docs don't state it can handle an integer.

This was an issue in two models:
-pki-role-engine.js
-mfa-methods.js

For both of those models, because the docs state a default, I amended their models to show them setting this defaultValue so the user knows that no matter what, if they press "Create" a defaultValue is being set.

[hellobontempo]

thanks for tackling! just some small questions/fixes for comments

[hellobontempo]

thanks for adding this comment! - small typo here! sting

[hellobontempo]

Thank you for remembering to update the docs! I was going to suggest updating the format to @param {type} paramName

buuut...I think we tend to do that when glimmerizing so probably fine to skip for now

[Monkeychip]

I know, I actually already attempted to glimmerize at my look into the problem. Had the exact same thought you did, but thought just in case any backporting needs to be done, I'll keep these two separate.

[hellobontempo]

this second part of this is a little unclear to me

if defaultValue is NOT set, do not display defaultValue

does this mean if defaultValue is NOT set, time input will be left blank?

[hellobontempo]

super nit: small typo here, should be: "than what the component shows on init."

but on second thought, not sure if we need to have that second sentence as it might cause confusion later. especially now that the problem is being solved, plus we have the git history to return to if we are ever wondering why we removed 30

[Monkeychip]

Works for me, I'll take out the second sentence.