[wpilib] Add SmartDashboard::PutData() reference overload

[calcmogul]

No description provided.

[PeterJohnson]

Historically we used a pointer here to indicate that the lifetime of the passed-in object mattered (e.g. because we store that pointer and call it later). It makes it at least somewhat more obvious that you should think about the lifetime of the thing you're passing (e.g. you shouldn't pass a local variable). What's the advantage of having the reference overload?

[calcmogul]

Historically we used a pointer here to indicate that the lifetime of the passed-in object mattered

I highly doubt our target audience is picking up on that nuance, especially since we don't explain that convention anywhere.

What's the advantage of having the reference overload?

The same advantages of providing reference overloads for constructors: it's more idiomatic, and our users don't have to remember to spam prefix ampersands to get their code to compile.

[spacey-sooty]

It makes it at least somewhat more obvious that you should think about the lifetime of the thing you're passing (e.g. you shouldn't pass a local variable).

To you or another WPILib maintainer? Sure. To a 14 year old who learnt C++ two weeks ago? Hell no. We were a C++ team until recently and as much as we tried to teach students about pointers and how memory worked it's a difficult concept to get through to people, they won't get this nuance they'll just do whatever they can to make their code compile (so just add an ampersand and never grasp the meaning of it).

I think this PR is fine as is itd just make students lives a bit easier, it doesn't allow them to make a mistake they couldn't before.