fix(DBComponentField) Swapped to using getValue

[nyeholt]

Using forTemplate causes some field types to change the underlying value when evaluating the returned data value (ie nl2br, or htmlencoding). This may be a convenient default for some things, but in a general sense causes terrible problems for things like form fields. Those areas that do need it can call the relevant things (like .ATT, .XML) from the template

[nyeholt]

@JoshuaCarter adding you on this because I kinda recall you working on the component stuff recently so you may have some insight as to why it uses forTemplate (cause I don't! :D)

[JoshuaCarter]

My exposure was limit to the ComponentService area of things.

That said, a quick squiz at the default DBField types suggests that DBString is the only one doing something in forTemplate that would be impacted by this change (return nl2br(parent::forTemplate());).

Have you tested this with DBString? If not, it might be worth testing, and if needed forTemplate can be used just for DBString?

[nglasl]

@nyeholt this one needs your input before it can be merged.