[1.x] Add Support for Custom Periods

[devajmeireles]

This PR aims to introduce support for custom periods via config file.

Demonstration

The config file:

/*
|--------------------------------------------------------------------------
| Pulse Periods
|--------------------------------------------------------------------------
|
| The following array lists the "periods" that will be available to select
| from the Pulse dashboard. You may modify this array as you wish, but
| ensure that the key is the period and the value is the hours.
|
*/

'periods' => [
    '1h' => 1,
    '6h' => 6,
    '24h' => 24,
    '7d' => 168,

    // customs 👇🏻 

    '30d' => 720,
    '7w' => 1_176,
],

The dashboard:

Note

Although with this PR the name of the period-related prefixes will be changed, for example: 6_hours to 6h, I don't believe there will be any breaking changes. Also, we have the "default" period saved internally, to make this PR be compatible with published configuration files.

Tests

I haven't been able to identify an exact way to test this. All current tests continue to pass so I think this is sufficient. I'm open to suggestions on how to introduce tests.

[devajmeireles]

Perhaps this description should be updated for better clarification.

[devajmeireles]

I preferred to send the current $period as $current to Blade so there is no name conflict here

[taylorotwell]

Thanks for your pull request to Laravel!

Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.

If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!