add RSASecurID support

[milljm]

Initial commit to add rsasecure_login to conda-forge.
Note: This package requires a milestone conda/conda#10667

This is a work in progress. Aside from the obvious milestone requirement, I am not
sure I like the command name rsasecure_login.

Checklist

• Title of this PR is meaningful: e.g. "Adding my_nifty_package", not "updated meta.yaml".
• License file is packaged (see here for an example).
• Source is from official source.
• Package does not vendor other packages. (If a package uses the source of another package, they should be separate packages or the licenses of all packages need to be packaged).
• If static libraries are linked in, the license of the static library is packaged.
• Build number is 0.
• A tarball (url) rather than a repo (e.g. git_url) is used in your recipe (see here for more details).
• GitHub users listed in the maintainer section have posted a comment confirming they are willing to be listed there.
• When in trouble, please check our knowledge base documentation before pinging a team.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/rsasecure_login) and found it was in an excellent condition.

I do have some suggestions for making it better though...

For recipes/rsasecure_login:

• License is not an SPDX identifier (or a custom LicenseRef) nor an SPDX license expression.

Documentation on acceptable licenses can be found here.

[milljm]

I hereby state I will be the maintainer for rsasecure_login.

[conda-forge-linter]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipes/rsasecure_login) and found it was in an excellent condition.

[milljm]

Closing because the accompanying Conda change will not be allowed to happen in it's current state. I do see this as a good thing, as it broadens my scope to include not just one specific MFA branding.