Correcting issue with jQuery code that was resulting in focus always going to other value box on tab

on certain node forms.  Fixed by moving submit and after_build hooks to
pay_node.module proper.

- As a result, renamed theme_pay_progress_total to theme_pay_progress
- Cleaned up the layout a little bit

  and balance details
- Add activity history theme function
- First pass at cleaning up pay_transaction items.

- to php's type handling.

  payment activity for that transaction.
- Fix pay_load to accommodate pay_activity items.

element fields.

  pay_node_handler_field_pay_form_link.  This will prevent a needless join for
  this field.

- Add join routes between pay_form and node so that their fields can be
  correctly included during views

- Remove now-bogus 'notafield' definitions

- Add 'table' definitions on pfid/nid fields so that the correct join route is
  established.

  relationship.

  the 'view' op.
- Do not load a default pay_form object if the node has an nid but no related
  form.  This prevents us from "forcing" values onto nodes that don't have or
  want attached payment forms.

  This is useful in e.g. donations, where you'd have an amount-only block that
  POSTs to the full form page.

- Respect forms that are POSTed in such a manner by setting any values using a
  set_* function.  This is safe, assuming that these functions cleanly and
  securely set the request values and that the validator catches any invalid
  user input.

- Use (float) rather than (int) on the "total" query.

form display.  This will allow you to specify the amounts in a query string or
a POSTed value.

- Collect and pass along an optional form_type for payment forms (think 'build
  mode)

node/<nid>/pay (assuming that's what the handler was going to do)

  work on any payment-form-enabled-node.

  use the relationship data from nodes.

  payment activities and transactions.
- Create a table in pay_node to capture transactions for node-attached pay_forms

executed during key payment events:

- Call hooks at key transaction events:

  * When any pay primitive is created/updated
  * When a payment form has reached its goal (if applicable)
  * When a payment transaction is complete
- Implement hook_hook_info so that actions can be configured on the triggers page
- Sit on select hooks to effect the trigger-configured actions.

Provide per-content-type and per-node settings to create OR link to payment
forms.

This interim commit makes these changes available on the node type
administration page, and reflects them on the node edit page

A database update hook adds a 'method' column to the pay_form_node table, so
that we can preserve the integrity of the relationship if the linking-method
changes, and linked forms don't suddenly start getting all edited/clobbered
when you change from 'select' to 'create'

types.  This will allow us to re-use an individual form across multiple nodes.

Since each node will optionally reuse and existing form, Reporting against
the form, its amount to goals, etc. will be an aggregate of payments
made against each associated node.