Customize token flow OAuth expirations with a config lambda

At NationBuilder, we assign a custom expiration to access tokens derived from token-based OAuth. We do this because our authorization code tokens tend to have very high expirations, while our token-based access tokens have very short ones. This pull request solves this problem for us by enabling the user to define an expiration on each app. Since we placed this configuration option inside of a lambda, it could also dynamically customized to vary in different ways.

-David
There's two issues here:

1. By default, `custom_access_token_expires_in` seems to be `lambda { |_app| nil }`. This evaluates to `true`, so we'd never be running `server.access_token_expires_in`.
2. Let's do a normal `if else`, I think it will read better than the `end ||`.