Re-add PAM build tag back to tctl build

[strideynet]

Fixes #12547

I'm not sure if this is the best solution, but it fixes the bug for now. It may be difficult to fix this otherwise as tctl loads the main teleport config which checks for the inclusion of pam when configured, even if tctl itself may not leverage it.

Partially undoes #11666

We will need to ensure we backport this into the versions that the original PR was backported into.

[ravicious]

#11666 was an attempt to tackle some problems with building tsh on Windows (we had a conversation about it on Slack). The actual problem lied somewhere else: code in tsh imported code from lib/web, which is supposed to be imported by the teleport binary only. Since lib/web assumes that it runs on a unix-like system, there were problems with building tsh on Windows. This has been fixed in #11690.

Still, at the time we decided to clean up those tags since we deemed them unnecessary, we weren't aware that it may cause problems with tctl. So adding PAM to tctl back shouldn't make the original issue with tsh builds on Windows reoccur.

[ravicious]

Ah, and the original PR was backported to the v9 branch only, I added an appropriate label to this PR.

[github-actions]

@strideynet See the table below for backport results.

Branch	Result
branch/v9	Create PR