Fixed: Grey out password reset button for consistency

[akemidx]

When user has no email in their profile, the box is greyed out for consistency accross all buttons on the user profile

Type of change

Please delete options that are not relevant.

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Tested in local instance

Checklist:

• I have read the Contributing documentation available here: https://snipe-it.readme.io/docs/contributing-overview
• I have formatted this PR according to the project guidelines: https://snipe-it.readme.io/docs/contributing-overview#pull-request-guidelines
• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[what-the-diff]

• Added a new div element to the HTML
• Changed an existing form tag into another one with different attributes and content
• Removed two elements from the DOM tree: button, form
• Added three elements to the DOM tree: button, form, div

[snipe]

This looks almost perfect, thanks!

You have:

              @can('update', $user)
                 <div class="col-md-12" style="padding-top: 5px;">
                   @if (($user->activated == '1') && ($user->email != '') && ($user->ldap_import == '0'))
                       <div class="col-md-12" style="padding-top: 5px;">
                         <form action="{{ route('users.password',['userId'=> $user->id]) }}" method="POST">
                       <form action="{{ route('users.password',['userId'=> $user->id]) }}" method="POST">
                           {{ csrf_field() }}
                           <button style="width: 100%;" class="btn btn-sm btn-primary hidden-print">{{ trans('button.send_password_link') }}</button>
                         </form>
                       </div>
                       <button style="width: 100%;" class="btn btn-sm btn-primary hidden-print">{{ trans('button.send_password_link') }}</button>
                       </form>
                   @elseif(($user->activated == '1') && ($user->ldap_import == '0'))
                       <button style="width: 100%;" class="btn btn-sm btn-primary hidden-print" rel="noopener" disabled title="{{ trans('admin/users/message.user_has_no_email') }}">{{ trans('button.send_password_link') }}</button> 
                   @endif
                   </div>
                 @endcan

I have two small nits here:

1. We're creating a <div></div> container that will exist even if the button conditions don't, which could make the layout look a little weird.
2. We're repeating the same conditions in both the if and the else, so a more nested approach might make sense here.

In pseudo-code:

if admin can update the user

    // the user is active and their password is NOT handled via LDAP
   
 if (($user->activated == '1') &&  ($user->ldap_import == '0'))
        // set the div to hold the button here
        
         // user's email isn't blank
         if ($user->email != '') 
              // yummy button code here

         // the user does not have an email address but otherwise looks correct
        else 
              // disabled button with no form tags here

        endif

endif

[akemidx]

check for email has been nested inside the original conditions. div container moved to into the outside if statement

[snipe]

NOICE! Thanks!