[EMCAL-1152] EMCAL: Fix cpplint errors

[mhemmer-cern]

This commit includes changes to:

• DataFormats/Detectors/EMCA
• Detectors/EMCAL/base

Changes are mostly:

• Change of header guard name
• Addition of basic information (file, author, brief description)
• Removal of ROOT variables where easily possible (Double32_t and Float16_t was NOT changed)
• Clear declaration of previously seemingly magic numbers
• Additional includes to ensure independence of other header files
• Proper c++ style casting
• Single-parameter constructors were marked explicit.
• Removal of Unary operator& since they are dangerous

Why is unary operator& dangerous?
Example: let's say we have a class MyClass.
Now the Code:
MyClass obj;
MyClass* ptr = &obj; // gets the memory address of obj
seems logical and correct, however, if one has the unary operator& defined within the class to return a reference of some member MyMember of the class, we would have:
MyClass obj;
MyMember* ptr = &obj; // gets the memory address of member of obj
It is better to write a properly named function that returns a reference to the member if it is needed:
MyMember& currentMember() { return mMyMember; }

[github-actions]

REQUEST FOR PRODUCTION RELEASES:
To request your PR to be included in production software, please add the corresponding labels called "async-" to your PR. Add the labels directly (if you have the permissions) or add a comment of the form (note that labels are separated by a ",")

+async-label <label1>, <label2>, !<label3> ...

This will add <label1> and <label2> and removes <label3>.

The following labels are available
async-2023-pbpb-apass4
async-2023-pp-apass4
async-2024-pp-apass1
async-2022-pp-apass7
async-2024-pp-cpass0
async-2024-PbPb-apass1
async-2024-ppRef-apass1
async-2024-PbPb-apass2
async-2023-PbPb-apass5

[github-actions]

This PR did not have any update in the last 30 days. Is it still needed? Unless further action in will be closed in 5 days.